Triple
T34801067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Series pin |
E1003218
|
entity |
| Predicate | hasValueFor |
P21633
|
FINISHED |
| Object | historical significance |
—
|
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: historical significance | Statement: [World Series pin, hasValueFor, historical significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValueFor Context triple: [World Series pin, hasValueFor, historical significance]
-
A.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
B.
isValuedFor
chosen
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
C.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
D.
hasValueFocus
Indicates that a particular value or data item is the primary focus or point of emphasis within a given context or relationship.
-
E.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.