Triple
T32578371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolray Field |
E832710
|
entity |
| Predicate | tenantFormerNameChangeYear |
P174614
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Coolray Field, tenantFormerNameChangeYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tenantFormerNameChangeYear Context triple: [Coolray Field, tenantFormerNameChangeYear, 2018]
-
A.
tenantFormerName
Indicates that the specified name was previously used by the tenant before their current official name.
-
B.
legalNameChangeBackYear
Indicates the year in which an entity’s legal name was changed back to a previous or original name.
-
C.
issuerNameChangeYear
Indicates the year in which an issuer changed its official name.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
underwentNameChangeTo
Indicates that an entity previously known by one name has changed its name to the specified new name.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c640c85481909bdd34f36234a438 |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:04 a.m.