Triple
T8328861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Societas Europaea |
E195024
|
entity |
| Predicate | hasManagementSystemOptions |
P18551
|
FINISHED |
| Object | two-tier 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: two-tier system | Statement: [Societas Europaea, hasManagementSystemOptions, two-tier system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagementSystemOptions Context triple: [Societas Europaea, hasManagementSystemOptions, two-tier system]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
hasTypeOfManagement
chosen
Indicates that an entity is associated with or operates under a specified form or style of management.
-
C.
hasLocalManagement
Indicates that an entity is managed, administered, or overseen by an authority or management structure located within the same local area or jurisdiction.
-
D.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
E.
hasStationManagement
Indicates that one entity is responsible for managing, operating, or overseeing the activities and administration of a station associated with 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fb812508190aed8a283dacf712e |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.