Triple

T18506483
Position Surface form Disambiguated ID Type / Status
Subject Likert scale E452209 entity
Predicate commonResponseFormat P97013 FINISHED
Object strongly disagree to strongly agree 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: strongly disagree to strongly agree | Statement: [Likert scale, commonResponseFormat, strongly disagree to strongly agree]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonResponseFormat
Context triple: [Likert scale, commonResponseFormat, strongly disagree to strongly agree]
  • A. typicalResponse
    Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
  • B. responseExample chosen
    Indicates that one entity serves as an illustrative or sample response corresponding to another entity (such as a prompt, question, or situation).
  • C. globalResponse
    Indicates a reaction, policy, or set of actions taken collectively at an international or worldwide level in response to a particular event or situation.
  • D. possibleResponse
    Indicates that an entity is a valid or acceptable reply, answer, or reaction to another entity or situation.
  • E. typicalResponseFormula
    Indicates that there is a standard or characteristic formula that typically represents the response associated with the given entities or situation.
  • 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_69d8d386df84819092355ebb260d848e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5334266708190b59aca3a2218c095 completed April 19, 2026, 7:55 p.m.
PD Predicate disambiguation batch_69e469dbf5208190b6fc49e02a087f54 completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 11:36 a.m.