Triple
T97985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitaphone |
E1974
|
entity |
| Predicate | limitation |
P99
|
FINISHED |
| Object | discs could wear out or be damaged |
—
|
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: discs could wear out or be damaged | Statement: [Vitaphone, limitation, discs could wear out or be damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitation Context triple: [Vitaphone, limitation, discs could wear out or be damaged]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
C.
limitsOffice
Indicates that one entity imposes a restriction or cap on the scope, duration, or powers of another entity’s office or official position.
-
D.
license
Indicates that one entity has granted another entity formal permission or authorization to use, perform, or exploit something under specified terms.
-
E.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebe7b1c8190a6bfbf31dc7c7f07 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.