Triple
T698717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caméra d’Or |
E13949
|
entity |
| Predicate | runtimeRequirement |
P11374
|
FINISHED |
| Object | feature-length |
—
|
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: feature-length | Statement: [Caméra d’Or, runtimeRequirement, feature-length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimeRequirement Context triple: [Caméra d’Or, runtimeRequirement, feature-length]
-
A.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
B.
hostRequirement
chosen
Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
-
C.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
D.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
E.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0dd4afc81909e4e869356006f33 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.