Triple
T24575590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faraday Future |
E608093
|
entity |
| Predicate | announcedFirstProductionModelYear |
P61333
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Faraday Future, announcedFirstProductionModelYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedFirstProductionModelYear Context triple: [Faraday Future, announcedFirstProductionModelYear, 2017]
-
A.
firstProductionYear
Indicates the year in which something (such as a product, work, or item) was first produced.
-
B.
firstPrototypeYear
Indicates the year in which the first prototype of an entity was created or completed.
-
C.
productionModelDebut
chosen
Indicates the event or point in time when a model first enters official production or is publicly released as a production version.
-
D.
firstModelIntroduced
Indicates that one entity is the earliest or original model introduced in relation to another entity or context.
-
E.
firstArrivalYear
Indicates the calendar year in which an entity first arrived at or was initially present in a specified place or context.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a928896c8190af385755b1418ba6 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.