Triple
T23030183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAS Leaders’ Meeting |
E573434
|
entity |
| Predicate | hasAttendeeLevel |
P2393
|
FINISHED |
| Object | head of state |
—
|
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: head of state | Statement: [EAS Leaders’ Meeting, hasAttendeeLevel, head of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttendeeLevel Context triple: [EAS Leaders’ Meeting, hasAttendeeLevel, head of state]
-
A.
hasAudienceLevel
Indicates that something is intended for, suitable for, or targeted at an audience with a specific level of knowledge, experience, or proficiency.
-
B.
hasAttendanceType
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
C.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
D.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
-
E.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f184803e908190b1e58545b9c3d587 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.