Triple
T34123543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Belle Noiseuse |
E875208
|
entity |
| Predicate | alternativeVersionRunningTime |
P50227
|
FINISHED |
| Object | approximately 125 minutes |
—
|
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: approximately 125 minutes | Statement: [La Belle Noiseuse, alternativeVersionRunningTime, approximately 125 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeVersionRunningTime Context triple: [La Belle Noiseuse, alternativeVersionRunningTime, approximately 125 minutes]
-
A.
alternativeDuration
chosen
Indicates that there is an additional or substitute time span associated with an event or activity, differing from its primary or standard duration.
-
B.
alternativeVersionDirector
Indicates that one director is responsible for an alternative or variant version of a work relative to another director’s version.
-
C.
previousRuntime
Indicates that one runtime instance temporally preceded another runtime instance in execution order.
-
D.
alternateVersionTrait
Indicates that one entity represents an alternative version or variant of another, differing in certain traits or characteristics.
-
E.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:53 a.m.