Triple
T11783554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newman |
E280210
|
entity |
| Predicate | railConnectionPurpose |
P101561
|
FINISHED |
| Object | iron ore export to coastal ports |
—
|
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: iron ore export to coastal ports | Statement: [Newman, railConnectionPurpose, iron ore export to coastal ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railConnectionPurpose Context triple: [Newman, railConnectionPurpose, iron ore export to coastal ports]
-
A.
countryRailConnection
Indicates that there is a railway connection or service linking two countries.
-
B.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
E.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
- F. None of above. chosen
Provenance (4 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
| PDg | Predicate description generation | batch_69d8a8c07d648190b8650d31f3a15090 |
completed | April 10, 2026, 7:37 a.m. |
Created at: April 8, 2026, 9:42 p.m.