Triple
T18461870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar Racing |
E451055
|
entity |
| Predicate | constructorEntries |
P59623
|
FINISHED |
| Object | 85 |
—
|
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: 85 | Statement: [Jaguar Racing, constructorEntries, 85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorEntries Context triple: [Jaguar Racing, constructorEntries, 85]
-
A.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
-
B.
numberOfEntries
chosen
Indicates the total count of individual items, records, or instances associated with a given entity or context.
-
C.
notableConstructor
Indicates that an entity is a well-known or significant creator, builder, or originator of another entity.
-
D.
coreConstruct
Indicates a fundamental building or organizing relationship where one entity serves as the essential basis or primary component from which another entity is formed or structured.
-
E.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7fd9e081909bdf5c4aec2ba08d |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.