Triple
T1130234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden spikes (symbolic baseball cleat spikes) |
E23012
|
entity |
| Predicate | hasSymbolicValue |
P25306
|
FINISHED |
| Object | prestige |
—
|
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: prestige | Statement: [Golden spikes (symbolic baseball cleat spikes), hasSymbolicValue, prestige]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolicValue Context triple: [Golden spikes (symbolic baseball cleat spikes), hasSymbolicValue, prestige]
-
A.
containsSymbolicAct
Indicates that one entity includes or incorporates a symbolic action or gesture associated with another entity.
-
B.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
-
D.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
E.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
- F. None of above. chosen
Provenance (4 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.