Triple
T31046472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7S III |
E791138
|
entity |
| Predicate | recordingLimit |
P191100
|
FINISHED |
| Object | no 30-minute recording limit |
—
|
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: no 30-minute recording limit | Statement: [Sony α7S III, recordingLimit, no 30-minute recording limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingLimit Context triple: [Sony α7S III, recordingLimit, no 30-minute recording limit]
-
A.
laterMaximumRecordingTime
Indicates that one time or event has a greater (later) maximum allowable or recorded time than another for the same recording-related context.
-
B.
recordingPeriodRequirement
Indicates the required duration or time period over which records or data must be kept or maintained.
-
C.
maximumRecordedLength
Indicates the greatest length value that has been observed and recorded for the entity in question.
-
D.
recordDuration
Indicates the length of time for which something is recorded or captured.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- F. None of above. chosen
Provenance (4 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: April 29, 2026, 8:59 p.m.