Triple
T8314688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt Documents |
E194676
|
entity |
| Predicate | containsDirectiveOn |
P42339
|
FINISHED |
| Object | convening a constitutional convention |
—
|
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: convening a constitutional convention | Statement: [Frankfurt Documents, containsDirectiveOn, convening a constitutional convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDirectiveOn Context triple: [Frankfurt Documents, containsDirectiveOn, convening a constitutional convention]
-
A.
hasDirective
chosen
Indicates that one entity issues, contains, or is governed by a specific directive or instruction associated with another entity.
-
B.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
C.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f52c5cc8190b5a95ee0aa4ddda5 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.