Triple
T634023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion Assembly |
E15982
|
entity |
| Predicate | hasProductionFocus |
P31
|
FINISHED |
| Object | small cars |
—
|
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: small cars | Statement: [Orion Assembly, hasProductionFocus, small cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductionFocus Context triple: [Orion Assembly, hasProductionFocus, small cars]
-
A.
hasMajorProductionSystem
Indicates that an entity primarily operates, utilizes, or is characterized by a particular major production system.
-
B.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
-
C.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
hasArtisticFocus
Indicates that an entity’s primary artistic attention, theme, or specialization is directed toward a particular subject, style, or medium.
-
E.
hasEditorialFocus
Indicates that an entity (such as a publication or section) is primarily concerned with or oriented around a particular editorial topic, theme, or subject area.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec3b6488190aa0dce216c089a2e |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.