Triple
T37507755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Idyllia |
E932140
|
entity |
| Predicate | belongsToCovenantSystem |
P201876
|
FINISHED |
| Object | neutral city of Oribos |
—
|
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: neutral city of Oribos | Statement: [The Idyllia, belongsToCovenantSystem, neutral city of Oribos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCovenantSystem Context triple: [The Idyllia, belongsToCovenantSystem, neutral city of Oribos]
-
A.
covenantSystemFeature
Indicates a relationship where a covenant includes, specifies, or is associated with a particular system feature or functionality.
-
B.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
-
C.
linkedToCovenantTightness
Indicates that one entity is associated with, or determined by, the strictness or tightness of a covenant’s terms or conditions.
-
D.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
E.
belongsToQuadrantSystem
Indicates that something is organized or classified within a coordinate or partitioning scheme that is divided into four quadrants.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: May 3, 2026, 4:17 p.m.