Triple
T13106918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USAR19000084 |
E310865
|
entity |
| Predicate | appliesToRecordingType |
P15615
|
FINISHED |
| Object | sound recording |
—
|
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: sound recording | Statement: [USAR19000084, appliesToRecordingType, sound recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToRecordingType Context triple: [USAR19000084, appliesToRecordingType, sound recording]
-
A.
recordingType
chosen
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
B.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
-
C.
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.
-
D.
mayBeRecordedAs
Indicates that something can optionally be documented or stored in a recorded form, but is not required to be.
-
E.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98154c9f48190aeca779d97151759 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.