Triple
T6120141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief |
E136460
|
entity |
| Predicate | typicallyInteractsWith |
P25924
|
FINISHED |
| Object | legislature on war powers |
—
|
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: legislature on war powers | Statement: [Commander-in-Chief, typicallyInteractsWith, legislature on war powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyInteractsWith Context triple: [Commander-in-Chief, typicallyInteractsWith, legislature on war powers]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
interactsWithGroup
chosen
Indicates that an entity engages in actions or exchanges with a collective group of other entities.
-
D.
principalInterlocutor
Indicates that one entity serves as the main or primary conversational partner or speaker in an interaction with another entity.
-
E.
acquaintanceOf
Indicates that one entity knows another in a casual or non-intimate way, without implying close friendship or strong personal ties.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bef8dc08190b917ad7209188c62 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.