Triple
T28946994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangalacharan |
E730606
|
entity |
| Predicate | positionInRecital |
P86740
|
FINISHED |
| Object | opening item |
—
|
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: opening item | Statement: [Mangalacharan, positionInRecital, opening item]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRecital Context triple: [Mangalacharan, positionInRecital, opening item]
-
A.
positionInPerformance
chosen
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
B.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
C.
positionInFestival
Indicates the specific role, slot, or placement an entity holds within the structure or schedule of a festival.
-
D.
performerPosition
Indicates the spatial or role-based placement of a performer relative to a performance context or other participants.
-
E.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 8:41 a.m.