Triple
T6777266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apolista language |
E155588
|
entity |
| Predicate | hasSpeakersToday |
P72733
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Apolista language, hasSpeakersToday, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakersToday Context triple: [Apolista language, hasSpeakersToday, no]
-
A.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
B.
currentSpeakers
Indicates that the referenced entities are the ones who are presently speaking or holding the floor at a given moment.
-
C.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
-
D.
speakers
Indicates that one or more entities produce spoken language or vocal communication, typically addressing an audience or participating in a conversation.
-
E.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26725208190b64935cfd08b2aff |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d182213c819086fcbbfd3d64d80b |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:13 p.m.