Triple
T35351786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longinus |
E1020898
|
entity |
| Predicate | onomaComponent |
P14071
|
FINISHED |
| Object | cognomen in 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: cognomen in Roman tria nomina system | Statement: [Longinus, onomaComponent, cognomen in Roman tria nomina system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onomaComponent Context triple: [Longinus, onomaComponent, cognomen in Roman tria nomina system]
-
A.
onomaType
Indicates a classification or type relationship associated with a name or designation between entities.
-
B.
onomaStructure
Indicates a structural or organizational relationship defined or named by a specific designation within a system or framework.
-
C.
component1
chosen
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
D.
sovereignComponent
Indicates that one entity functions as a constituent part of a larger sovereign whole, such as a state, polity, or authority.
-
E.
componentAct
Indicates that an action or behavior is performed by a component as part of a larger system or process.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.