Triple

T7689886
Position Surface form Disambiguated ID Type / Status
Subject Ars Poetica E174217 entity
Predicate keyLine P78726 FINISHED
Object "A poem should not mean / But be" 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: "A poem should not mean / But be" | Statement: [Ars Poetica, keyLine, "A poem should not mean / But be"]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: keyLine
Context triple: [Ars Poetica, keyLine, "A poem should not mean / But be"]
  • A. keyRite
    Indicates that an entity performs or is associated with a ritual, ceremony, or formal procedure involving a key (literal or symbolic).
  • B. criticalLine
    Indicates that one entity is a crucial or decisive line (such as a boundary, path, or threshold) whose state or position significantly affects the other entity or overall system.
  • C. yardLine
    Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
  • D. keyRule
    Indicates that a rule or principle functions as a key or primary governing condition for something.
  • E. key
    Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
  • F. None of above. chosen

Provenance (4 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_69c6995966348190939e6c37ba272c06 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c706d1f0208190bc5b695aa5736244 completed March 27, 2026, 10:38 p.m.
PD Predicate disambiguation batch_69c70163dea88190ae729df50e63dfd7 completed March 27, 2026, 10:15 p.m.
PDg Predicate description generation batch_69c706d0c1708190a3e74523997814b8 completed March 27, 2026, 10:38 p.m.
Created at: March 27, 2026, 4:02 p.m.