Triple
T4384646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vin |
E99211
|
entity |
| Predicate | isNotTypically |
P40931
|
FINISHED |
| Object | formal legal name |
—
|
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: formal legal name | Statement: [Vin, isNotTypically, formal legal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotTypically Context triple: [Vin, isNotTypically, formal legal name]
-
A.
notTypically
chosen
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
B.
notTypicallyUsedFor
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
isNotIndicatedFor
Indicates that a treatment, action, or option is not recommended or appropriate for a particular condition, situation, or entity.
-
E.
typicallyLack
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.