Triple
T9467235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant Chain |
E228300
|
entity |
| Predicate | hasDiplomaticForm |
P88278
|
FINISHED |
| Object | council meetings |
—
|
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: council meetings | Statement: [Covenant Chain, hasDiplomaticForm, council meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiplomaticForm Context triple: [Covenant Chain, hasDiplomaticForm, council meetings]
-
A.
hasDiplomaticFormat
Indicates that a diplomatic communication, document, or interaction follows a specific recognized diplomatic format or protocol.
-
B.
hasDiplomaticLevel
Indicates the degree or status of formal diplomatic relations that exists between two entities.
-
C.
hasDiplomaticMission
Indicates that one entity maintains an official diplomatic representation, such as an embassy or mission, in the territory or jurisdiction of another entity.
-
D.
hasDiplomaticTheme
Indicates that something involves or centers on diplomatic relations, negotiations, or international political interactions.
-
E.
hasDiplomaticRankHead
Indicates that an entity serving as a head (e.g., of a mission or organization) holds a specific diplomatic rank.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdd7d048190930a15cb2a2d99ea |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:53 p.m.