Triple
T31916765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pison |
E814852
|
entity |
| Predicate | onomaStructure |
P172728
|
FINISHED |
| Object | Roman tria nomina system |
—
|
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: Roman tria nomina system | Statement: [Pison, onomaStructure, Roman tria nomina system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onomaStructure Context triple: [Pison, onomaStructure, Roman tria nomina system]
-
A.
onomaType
Indicates a classification or type relationship associated with a name or designation between entities.
-
B.
dominantStructure
Indicates that one structure exerts primary control, influence, or prominence over other related structures within a given context.
-
C.
topStructure
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
-
D.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
-
E.
majorStructure
Indicates that one entity functions as a primary or principal structural component or framework in relation to 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1ef9a84819092952e451b98987b |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: May 1, 2026, 12:02 a.m.