Triple
T6966134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloria |
E161491
|
entity |
| Predicate | airingFormat |
P66878
|
FINISHED |
| Object | multi-camera |
—
|
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: multi-camera | Statement: [Gloria, airingFormat, multi-camera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airingFormat Context triple: [Gloria, airingFormat, multi-camera]
-
A.
televisionFormat
chosen
Indicates the specific type or style of television program or production format associated with an entity.
-
B.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
C.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
D.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
E.
broadcastsInFormat
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db121174819098e73e45f6c9cc91 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.