Triple
T169105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Blue |
E3078
|
entity |
| Predicate | conferenceTitlesApproximate |
P557
|
FINISHED |
| Object | 5+ |
—
|
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: 5+ | Statement: [Big Blue, conferenceTitlesApproximate, 5+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceTitlesApproximate Context triple: [Big Blue, conferenceTitlesApproximate, 5+]
-
A.
conferenceTitles
chosen
Indicates a relationship where one entity (such as a conference event or series) is associated with the titles under which it is or has been held.
-
B.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
C.
conference2
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
-
D.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
-
E.
parallelConferenceFullName
Indicates that one conference’s full official name is that of another conference held in parallel (at the same time or as a counterpart event).
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258b6f4f88190b1264bbbeb19a29e |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25665f5b8819096ca3e084faf976e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.