Triple
T15842694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brabham (historical) |
E384135
|
entity |
| Predicate | periodOfOwnershipEnd |
P88884
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Brabham (historical), periodOfOwnershipEnd, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfOwnershipEnd Context triple: [Brabham (historical), periodOfOwnershipEnd, 1987]
-
A.
ownershipEnd
Indicates the point or event at which an entity’s ownership of another entity ceases or is terminated.
-
B.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
-
C.
dateOfAbandonment
Indicates the specific date on which something (such as a place, project, or object) was formally or effectively abandoned or discontinued.
-
D.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
holderEndDate
chosen
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
- F. None of above.
Provenance (3 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e88ff08190a1035269e8fdaa6a |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.