Triple
T7918254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronk's New Groove |
E183879
|
entity |
| Predicate | containsSegmentStructure |
P6241
|
FINISHED |
| Object | three-part story |
—
|
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: three-part story | Statement: [Kronk's New Groove, containsSegmentStructure, three-part story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSegmentStructure Context triple: [Kronk's New Groove, containsSegmentStructure, three-part story]
-
A.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
B.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
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.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
E.
hasMultipleSegments
chosen
Indicates that the referenced entity is composed of more than one distinct segment or section.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.