Triple
T35339657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Further |
E1020561
|
entity |
| Predicate | traveledAcross |
P44461
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Further, traveledAcross, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traveledAcross Context triple: [Further, traveledAcross, United States]
-
A.
traveledAs
Indicates that an entity moved from one place to another in the role, capacity, or identity specified by another entity (e.g., as a tourist, as a representative, as a refugee).
-
B.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
C.
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.
-
D.
traveledFor
Indicates that an entity moved or journeyed to a place or event for a specific purpose, reason, or activity.
-
E.
traveledToBy
Indicates that an entity has been traveled to or visited by another entity.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 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:03 p.m.