Triple
T16470205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Four |
E400039
|
entity |
| Predicate | dominantInIndustry |
P67914
|
FINISHED |
| Object | rail transport |
—
|
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: rail transport | Statement: [Big Four, dominantInIndustry, rail transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantInIndustry Context triple: [Big Four, dominantInIndustry, rail transport]
-
A.
dominatedSector
chosen
Indicates that one entity exercises prevailing control or influence over a particular sector relative to others.
-
B.
dominantOccupation
Indicates the primary type of work or profession that most characterizes an entity’s economic or labor activity.
-
C.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
D.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
E.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dcfed6c8190b8dbe4b65b0ab817 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.