Triple
T15396576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book III of De fide |
E368191
|
entity |
| Predicate | hasStructureRole |
P118631
|
FINISHED |
| Object | major section |
—
|
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: major section | Statement: [Book III of De fide, hasStructureRole, major section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureRole Context triple: [Book III of De fide, hasStructureRole, major section]
-
A.
hasRoleInFormationOf
Indicates that an entity plays a specific role or function in the creation, development, or establishment of another entity or structure.
-
B.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
C.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
D.
hasGoverningRole
Indicates that one entity holds an official position of authority, control, or governance over another entity or domain.
-
E.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8c5d40819086622b70edcb6294 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.