Triple
T12800810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foreign Service Impasse Disputes Panel |
E306011
|
entity |
| Predicate | resolutionMethods |
P21949
|
FINISHED |
| Object | fact-finding |
—
|
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: fact-finding | Statement: [Foreign Service Impasse Disputes Panel, resolutionMethods, fact-finding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionMethods Context triple: [Foreign Service Impasse Disputes Panel, resolutionMethods, fact-finding]
-
A.
resolutionMethod
chosen
Indicates the specific approach, technique, or process used to resolve a problem, conflict, or issue.
-
B.
resolutionMechanism
Indicates the method, process, or system used to resolve a conflict, issue, or discrepancy between entities.
-
C.
resolutionIdea
Indicates a proposed method, plan, or approach intended to resolve or address a particular issue, conflict, or problem.
-
D.
resolutionType
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
-
E.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7d3f5c8190bf01bef5d263ca26 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.