Triple
T6943115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mikado |
E160725
|
entity |
| Predicate | openingNumber |
P27312
|
FINISHED |
| Object | If you want to know who we are |
—
|
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: If you want to know who we are | Statement: [The Mikado, openingNumber, If you want to know who we are]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingNumber Context triple: [The Mikado, openingNumber, If you want to know who we are]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingBegan
Indicates that the process of opening something has started.
-
C.
openingDetail
Indicates the specific manner, context, or characteristics of how an opening (such as a beginning, start, or initial access point) occurs or is carried out between entities.
-
D.
openingAnswer
chosen
Indicates that an entity provides an initial or first response in a dialogue, interaction, or sequence of answers.
-
E.
openingFunction
Indicates that one entity serves as the initial or primary function, role, or operation that begins or initiates a process, sequence, or interaction involving another entity.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.