Triple
T17035062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keystone Division |
E413297
|
entity |
| Predicate | symbolDerivedFrom |
P909
|
FINISHED |
| Object | Pennsylvania state nickname "Keystone State" |
—
|
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: Pennsylvania state nickname "Keystone State" | Statement: [Keystone Division, symbolDerivedFrom, Pennsylvania state nickname "Keystone State"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolDerivedFrom Context triple: [Keystone Division, symbolDerivedFrom, Pennsylvania state nickname "Keystone State"]
-
A.
symbolLinked
Indicates a relationship where one symbol is connected or associated with another symbol, typically to show reference, correspondence, or linkage between them.
-
B.
symbolReferenced
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
C.
symbolVariant
Indicates that one symbol is an alternative graphical or stylistic form of another symbol.
-
D.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
E.
symbolIs
Indicates that one entity serves as the symbolic representation or sign of another entity.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f05824819091d2aa02e5591e26 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.