Triple
T18379625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dacia |
E446408
|
entity |
| Predicate | notableModelType |
P94682
|
FINISHED |
| Object | compact sedan |
—
|
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: compact sedan | Statement: [Dacia, notableModelType, compact sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableModelType Context triple: [Dacia, notableModelType, compact sedan]
-
A.
notableModel
Indicates that an entity is a particularly important, influential, or exemplary instance or version within a broader category or system.
-
B.
notableTypeOf
chosen
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
C.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
D.
notableStoreType
Indicates that a store is particularly recognized or distinguished for being of a specified type (e.g., a notable example of that kind of store).
-
E.
notableModelDeveloped
Indicates that an entity is recognized for having created, designed, or developed a significant or noteworthy model.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51799e0f4819089e8af04888549bf |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.