Triple
T16813415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee Room 29 |
E408673
|
entity |
| Predicate | audioRecorded |
P9348
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Committee Room 29, audioRecorded, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioRecorded Context triple: [Committee Room 29, audioRecorded, yes]
-
A.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
B.
soundRecordingBy
Indicates that a sound recording was created, performed, or produced by a particular agent (such as an artist, band, or producer).
-
C.
recorded
chosen
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
D.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
-
E.
hasVoiceRecorder
Indicates that one entity possesses or is equipped with a voice recording device or capability in relation to another entity or context.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e01fb8819081cf2c08f29448da |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.