Triple
T25742751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewloe |
E648261
|
entity |
| Predicate | hasNearbyHeadquarters |
P174224
|
FINISHED |
| Object | Redrow plc |
—
|
NE NERFINISHED |
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: Redrow plc | Statement: [Ewloe, hasNearbyHeadquarters, Redrow plc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHeadquarters Context triple: [Ewloe, hasNearbyHeadquarters, Redrow plc]
-
A.
nearHeadquartersOf
Indicates that one entity is located geographically close to the headquarters of another entity.
-
B.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the specified place.
-
C.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
-
D.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
-
E.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 22, 2026, 3:46 a.m.