Triple
T2279439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discourse on the Arts and Sciences |
E51247
|
entity |
| Predicate | positionOnCompetitionQuestion |
P16114
|
FINISHED |
| Object | negative |
—
|
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: negative | Statement: [Discourse on the Arts and Sciences, positionOnCompetitionQuestion, negative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCompetitionQuestion Context triple: [Discourse on the Arts and Sciences, positionOnCompetitionQuestion, negative]
-
A.
positionOnRace
chosen
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
-
B.
subjectPosition
Indicates the spatial or logical position of a subject relative to a reference frame, context, or other entities.
-
C.
positionOnIssue
Indicates the stance or viewpoint an entity holds regarding a specific issue or topic.
-
D.
positionOnReason
Indicates that one entity holds a particular stance, justification, or rationale concerning another entity or issue.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2194150819083156e4dcd45a423 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.