Triple
T20046547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G8 summit meetings |
E497571
|
entity |
| Predicate | hasWorkingLevel |
P138504
|
FINISHED |
| Object | sherpa meetings |
—
|
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: sherpa meetings | Statement: [G8 summit meetings, hasWorkingLevel, sherpa meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingLevel Context triple: [G8 summit meetings, hasWorkingLevel, sherpa meetings]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
worksAtLevel
Indicates that an entity performs work or holds a role at a specified hierarchical or organizational level.
-
C.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
D.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
E.
hasUnitLevel
Indicates that something is associated with, measured at, or applicable to a specific unit level within a larger hierarchy or scale.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632a5e888190ade41657ffd057f6 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:37 p.m.