Triple
T1453556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snap the Whip |
E31346
|
entity |
| Predicate | hasCompositionFeature |
P182
|
FINISHED |
| Object | diagonal line of children |
—
|
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: diagonal line of children | Statement: [Snap the Whip, hasCompositionFeature, diagonal line of children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompositionFeature Context triple: [Snap the Whip, hasCompositionFeature, diagonal line of children]
-
A.
hasCloudComposition
Indicates that an atmospheric body or region possesses a specific composition or makeup of clouds.
-
B.
isComposite
Indicates that an entity is made up of multiple components or parts combined into a single whole.
-
C.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
D.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
E.
hasDistinctFeature
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57e82d48190a30a4512f39f5de0 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.