Triple
T9890788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadrilateral Security Dialogue |
E181443
|
entity |
| Predicate | experiencedHiatus |
P71228
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Quadrilateral Security Dialogue, experiencedHiatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedHiatus Context triple: [Quadrilateral Security Dialogue, experiencedHiatus, yes]
-
A.
hiatusPeriod
Indicates a temporary pause or interruption in an ongoing process, activity, or state, typically bounded by a start and end time.
-
B.
hiatus
chosen
Indicates a temporary pause, break, or interruption in an ongoing process, activity, or sequence.
-
C.
experiencedProcess
Indicates that an entity has undergone or participated in a particular process or event.
-
D.
experiencedFailure
Indicates that an entity has undergone or encountered a failure in performing an action, achieving a goal, or maintaining a desired state.
-
E.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb47dfa908190884e96e5e5d6f41f |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.