Triple
T27026736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Session C |
E680807
|
entity |
| Predicate | isSpecialSession |
P161783
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Special Session C, isSpecialSession, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpecialSession Context triple: [Special Session C, isSpecialSession, true]
-
A.
canBeCalledIntoSpecialSessionBy
Indicates that one entity has the authority to convene or summon another entity into a special session.
-
B.
inSessionDuring
Indicates that an entity is actively engaged in or part of a session throughout a specified time period.
-
C.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
D.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
E.
isConferenceSpecific
Indicates that something applies only within the context of a particular conference and does not hold generally outside that specific event.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f622323540819085ba63fa3ab9199d |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 7:11 a.m.