Triple
T27251296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictish double-disc and Z-rod |
E687492
|
entity |
| Predicate | hypothesizedMeaning |
P10718
|
FINISHED |
| Object | possible symbol of rank or status |
—
|
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: possible symbol of rank or status | Statement: [Pictish double-disc and Z-rod, hypothesizedMeaning, possible symbol of rank or status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hypothesizedMeaning Context triple: [Pictish double-disc and Z-rod, hypothesizedMeaning, possible symbol of rank or status]
-
A.
possibleMeaning
chosen
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
B.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
C.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
D.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
E.
nameMeaningHypothesis
Indicates a proposed or inferred meaning associated with a given name.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f626b5b99081908d173630fade1f36 |
completed | May 2, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:45 a.m.