Triple
T32620878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destricted |
E833917
|
entity |
| Predicate | hasSegmentDirector |
P83424
|
FINISHED |
| Object | Matthew Barney |
—
|
NE NERFINISHED |
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: Matthew Barney | Statement: [Destricted, hasSegmentDirector, Matthew Barney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSegmentDirector Context triple: [Destricted, hasSegmentDirector, Matthew Barney]
-
A.
segmentDirector
chosen
Indicates that one entity serves as the director responsible for a specific segment or portion of a larger production or program involving another entity.
-
B.
hasDeFactoSegmentWith
Indicates that one entity includes or is associated with a segment that functions in practice (de facto) as part of it, even if not formally or legally defined as such.
-
C.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, or sequence).
-
D.
hasOwnerSegment
Indicates that something is associated with, or belongs to, a specific owner-defined segment or partition.
-
E.
hasSegmentBasedOn
Indicates that one segment is derived from, modeled after, or constructed using another segment as its basis.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 1, 2026, 1:06 a.m.