Triple
T29215787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Aerospace |
E740663
|
entity |
| Predicate | acquisitionDateApproximate |
P2754
|
FINISHED |
| Object | early 1990s |
—
|
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: early 1990s | Statement: [Ford Aerospace, acquisitionDateApproximate, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionDateApproximate Context triple: [Ford Aerospace, acquisitionDateApproximate, early 1990s]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
yearDeliveredApprox
Indicates that the year an item or entity was delivered is known only approximately, rather than as an exact calendar year.
-
E.
designedApproximately
Indicates that one entity was created, planned, or engineered to an estimated or imprecise degree in relation to another entity or specification.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 12:13 p.m.