Triple
T6243554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Model B (1932) |
E139659
|
entity |
| Predicate | successorEngineFamily |
P69275
|
FINISHED |
| Object | Ford inline-four successors |
—
|
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: Ford inline-four successors | Statement: [Ford Model B (1932), successorEngineFamily, Ford inline-four successors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEngineFamily Context triple: [Ford Model B (1932), successorEngineFamily, Ford inline-four successors]
-
A.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
-
B.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
C.
successorModel
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
D.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
E.
successorSoftware
Indicates that one software product directly follows and replaces another as its newer version or update.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631b32308190a8211043d1caa6e6 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:23 p.m.