Triple
T27868464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin |
E704424
|
entity |
| Predicate | notableModelClass |
P202042
|
FINISHED |
| Object | small family 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 family cars | Statement: [Austin, notableModelClass, small family cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableModelClass Context triple: [Austin, notableModelClass, small family cars]
-
A.
notableModel
Indicates that an entity is a particularly important, influential, or exemplary instance or version within a broader category or system.
-
B.
notableClass
Indicates that an entity belongs to a particularly important, distinguished, or otherwise noteworthy class or category within a given classification system.
-
C.
modelClass
Indicates that one entity serves as the class, type, or template definition for another entity that is an instance or implementation of it.
-
D.
notableModelDeveloped
Indicates that an entity is recognized for having created, designed, or developed a significant or noteworthy model.
-
E.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
| PDg | Predicate description generation | batch_6a0049e352248190b0a0bb7dfe572c2c |
completed | May 10, 2026, 9:03 a.m. |
Created at: April 27, 2026, 6:22 p.m.