Triple
T23570540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tourist Trophy (sports car race) |
E580092
|
entity |
| Predicate | typicalEntrant |
P12352
|
FINISHED |
| Object | major automobile manufacturers |
—
|
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: major automobile manufacturers | Statement: [Tourist Trophy (sports car race), typicalEntrant, major automobile manufacturers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntrant Context triple: [Tourist Trophy (sports car race), typicalEntrant, major automobile manufacturers]
-
A.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
B.
typicalCandidate
chosen
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
C.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
D.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd259e4819094b09f3ed76664ea |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:36 p.m.