Triple

T9377392
Position Surface form Disambiguated ID Type / Status
Subject The Arrangement E225683 entity
Predicate hasIntricateComposition P28756 FINISHED
Object true — 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: true | Statement: [The Arrangement, hasIntricateComposition, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIntricateComposition
Context triple: [The Arrangement, hasIntricateComposition, true]
  • A. hasComplex
    Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
  • B. hasComplexity chosen
    Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
  • 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. hasReasoningComplexity
    Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
  • E. compositionalFeature
    Indicates that one entity is a structural or constituent feature that forms part of the composition or makeup of another entity.
  • 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_69ca842d8ee88190aaaa639aa953185d completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd50ab658c8190b23b2a97d15bb3f1 completed April 1, 2026, 5:06 p.m.
PD Predicate disambiguation batch_69cc7a6c733881908aa3070830c2100b completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:44 p.m.