Triple
T15510968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redland Field |
E368706
|
entity |
| Predicate | openedAsRedlandField |
P118935
|
FINISHED |
| Object | 1912 |
—
|
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: 1912 | Statement: [Redland Field, openedAsRedlandField, 1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsRedlandField Context triple: [Redland Field, openedAsRedlandField, 1912]
-
A.
openedAsRAFStation
Indicates that a facility or location was initially established and began operation as a Royal Air Force (RAF) station.
-
B.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
C.
openedAsComplex
Indicates that one entity was inaugurated or began operation specifically as a multi-part or multi-use complex, rather than as a single standalone facility.
-
D.
openedAsRedLineStation
Indicates that a station began operation specifically as part of the Red Line when it first opened.
-
E.
openedAsBRT
Indicates that a transit service, corridor, or route was initially launched or began operation specifically as a bus rapid transit (BRT) system.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:55 a.m.