Triple
T7455860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Town Car |
E172119
|
entity |
| Predicate | commonConfiguration |
P2093
|
FINISHED |
| Object | chauffeur-driven vehicle |
—
|
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: chauffeur-driven vehicle | Statement: [Lincoln Town Car, commonConfiguration, chauffeur-driven vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonConfiguration Context triple: [Lincoln Town Car, commonConfiguration, chauffeur-driven vehicle]
-
A.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
B.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
D.
configuration
chosen
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
E.
commonAttribute
Indicates that two or more entities share the same specified attribute or property.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3af58dc819093fb0482482779a3 |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:15 p.m.