Triple
T32215737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computational Learning Theory |
E822917
|
entity |
| Predicate | hasInfluentialConference |
P200367
|
FINISHED |
| Object | COLT |
—
|
NE NERFINISHED |
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: COLT | Statement: [Computational Learning Theory, hasInfluentialConference, COLT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfluentialConference Context triple: [Computational Learning Theory, hasInfluentialConference, COLT]
-
A.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
B.
hadConference
Indicates that a conference event took place involving the specified entities (such as participants, organizations, or locations).
-
C.
usedInConference
Indicates that something (such as a method, tool, or material) is employed or applied within the context of a particular conference.
-
D.
hasConferenceType
Indicates that an entity is associated with or classified by a specific type or category of conference.
-
E.
conferencesCovered
Indicates that one entity has reported on, documented, or provided coverage of one or more conferences associated with another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
| PDg | Predicate description generation | batch_69ff84dec2848190b67a497d025c8880 |
completed | May 9, 2026, 7:02 p.m. |
Created at: May 1, 2026, 12:37 a.m.