Triple
T35482361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer |
E1025500
|
entity |
| Predicate | travelsBeyond |
P44461
|
FINISHED |
| Object | The Wall |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: The Wall | Statement: [Summer, travelsBeyond, The Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelsBeyond Context triple: [Summer, travelsBeyond, The Wall]
-
A.
cosmologicalTravel
Indicates travel or movement that occurs across cosmic or interstellar scales, such as between planets, star systems, or galaxies.
-
B.
travelsAbroad
Indicates that an entity goes to or spends time in a foreign country outside its usual nation of residence.
-
C.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
-
D.
journeysAcross
chosen
Indicates that an entity travels or moves from one side or area to another, passing over or through an intervening space or boundary.
-
E.
travelBetweenUniverses
Indicates traveling or moving from one universe or dimension to another.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.