Triple
T4757676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comedìa |
E105626
|
entity |
| Predicate | symbolicStructure |
P29171
|
FINISHED |
| Object | Trinitarian numerology |
—
|
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: Trinitarian numerology | Statement: [Comedìa, symbolicStructure, Trinitarian numerology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicStructure Context triple: [Comedìa, symbolicStructure, Trinitarian numerology]
-
A.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
B.
hasSymbolicForm
chosen
Indicates that one entity serves as the symbolic representation or abstract form of another entity.
-
C.
grammaticalStructure
Indicates the way linguistic elements are organized and related within a sentence or phrase according to grammatical rules.
-
D.
dominantStructure
Indicates that one structure exerts primary control, influence, or prominence over other related structures within a given context.
-
E.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.