Triple
T1673852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinscroft |
E36185
|
entity |
| Predicate | partOfNetworkExpansion |
P31620
|
FINISHED |
| Object | Airport Line extension |
—
|
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: Airport Line extension | Statement: [Martinscroft, partOfNetworkExpansion, Airport Line extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfNetworkExpansion Context triple: [Martinscroft, partOfNetworkExpansion, Airport Line extension]
-
A.
expansionPartner
Indicates a relationship where one entity collaborates with another to support or drive its growth into new markets, regions, or domains.
-
B.
branchNetwork
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
-
C.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
D.
laterNetwork
Indicates that one network occurs or is established after another network in time.
-
E.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab271be3f4819091adcd745dec8159 |
completed | March 6, 2026, 7:12 p.m. |
Created at: March 4, 2026, 7:29 p.m.