Triple
T8193290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V4 |
E191365
|
entity |
| Predicate | hasWorkingFormat |
P81423
|
FINISHED |
| Object | summit meetings of heads of government |
—
|
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: summit meetings of heads of government | Statement: [V4, hasWorkingFormat, summit meetings of heads of government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingFormat Context triple: [V4, hasWorkingFormat, summit meetings of heads of government]
-
A.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
B.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
C.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c1d7aa48190adbbce88b3bed1a3 |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:42 p.m.