Triple
T29562686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford LTD |
E750078
|
entity |
| Predicate | becameSeparateModel |
P167452
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Ford LTD, becameSeparateModel, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameSeparateModel Context triple: [Ford LTD, becameSeparateModel, late 1960s]
-
A.
laterSeparatedFrom
Indicates that one entity became separated from another at a later time than some referenced separation event.
-
B.
wouldHaveBeenSeparatedFrom
Indicates a hypothetical or counterfactual situation in which one entity would have been divided, detached, or kept apart from another entity if certain conditions had occurred.
-
C.
introducedAsModel
Indicates that one entity is presented or identified to others in the role or capacity of a model.
-
D.
adoptedModel
Indicates that one entity has formally chosen, accepted, or implemented another entity as its preferred model or standard.
-
E.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1e64e8819080579603e5bcdeb7 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 5:21 p.m.