Triple
T25745835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F performance division |
E648341
|
entity |
| Predicate | letterFMeaning |
P47684
|
FINISHED |
| Object | Fuji Speedway |
—
|
NE NERFINISHED |
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: Fuji Speedway | Statement: [F performance division, letterFMeaning, Fuji Speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: letterFMeaning Context triple: [F performance division, letterFMeaning, Fuji Speedway]
-
A.
letterMeaning
chosen
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
B.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
C.
chantMeaning
Indicates that an entity performs or conveys the meaning or content of a chant in relation to another entity or context.
-
D.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
E.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1e9dd081908c70074c8aa49e51 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:51 a.m.