Triple
T27251329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class I symbol stones |
E687493
|
entity |
| Predicate | exampleSymbol |
P166646
|
FINISHED |
| Object | double-disc and Z-rod |
—
|
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: double-disc and Z-rod | Statement: [Class I symbol stones, exampleSymbol, double-disc and Z-rod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleSymbol Context triple: [Class I symbol stones, exampleSymbol, double-disc and Z-rod]
-
A.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
B.
symbolIs
Indicates that one entity serves as the symbolic representation or sign of another entity.
-
C.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
-
D.
systemSymbol
Indicates that one entity serves as the symbolic representation or notation used within a particular system for another entity or concept.
-
E.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 10:45 a.m.