Triple
T8652930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche 718 Boxster |
E205142
|
entity |
| Predicate | nameReference |
P35337
|
FINISHED |
| Object | Porsche 718 racing cars of the 1950s and 1960s |
—
|
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: Porsche 718 racing cars of the 1950s and 1960s | Statement: [Porsche 718 Boxster, nameReference, Porsche 718 racing cars of the 1950s and 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameReference Context triple: [Porsche 718 Boxster, nameReference, Porsche 718 racing cars of the 1950s and 1960s]
-
A.
namedIn
chosen
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
B.
nameOf
Indicates that one entity is the name or designation of another entity.
-
C.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
D.
symbolReferenced
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
E.
namedMember
Indicates that an entity is a member of a group, organization, or collection and is identified by a specific name within that membership context.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc484206d881908017897dada63124 |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:29 p.m.