Triple
T23797609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Dillon |
E588579
|
entity |
| Predicate | canTravelThrough |
P11198
|
FINISHED |
| Object | power lines |
—
|
LITERAL FINISHED |
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: power lines | Statement: [Max Dillon, canTravelThrough, power lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTravelThrough Context triple: [Max Dillon, canTravelThrough, power lines]
-
A.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
B.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
C.
connectsTravelBetween
Indicates a relationship where something (such as a route, service, or mode of transport) enables or provides travel between two locations.
-
D.
isPassedThroughBy
chosen
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
E.
withinTravelTo
Indicates that one location is close enough to another that traveling between them is feasible or practical within a specified limit (such as time or distance).
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dea2888190b3ff1c96da5cfefb |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:50 p.m.