Triple
T35482304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jojen Reed |
E1025499
|
entity |
| Predicate | journeysBeyond |
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: [Jojen Reed, journeysBeyond, the Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeysBeyond Context triple: [Jojen Reed, journeysBeyond, the Wall]
-
A.
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.
-
B.
journey
Indicates that an entity travels or moves from one place or state to another, typically over a period of time or distance.
-
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.
inspiredVoyage
Indicates that one entity’s ideas, actions, or example motivated another entity to undertake a particular journey or expedition.
-
E.
cosmologicalTravel
Indicates travel or movement that occurs across cosmic or interstellar scales, such as between planets, star systems, or galaxies.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.