Triple
T38012625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brunel family |
E948405
|
entity |
| Predicate | notableProjectAssociation |
P52042
|
FINISHED |
| Object | Great Western Railway |
E28420
|
NE 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: Great Western Railway | Statement: [Brunel family, notableProjectAssociation, Great Western Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProjectAssociation Context triple: [Brunel family, notableProjectAssociation, Great Western Railway]
-
A.
notableProjectFor
chosen
Indicates that a particular project is especially significant, prominent, or noteworthy for a given entity.
-
B.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
C.
notableProjectArea
Indicates that an entity has a significant or distinguished project specifically associated with a particular area or domain.
-
D.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
notableProjectCountry
Indicates that a country is associated with a notable project undertaken by the subject.
- F. None of above.
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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412ca2c05c8190bb1eff67b2c1ccbd |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.