Triple
T31947373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mister Negative |
E815687
|
entity |
| Predicate | runsOrganization |
P91582
|
FINISHED |
| Object | FEAST Project |
—
|
NE NERFINISHED |
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: FEAST Project | Statement: [Mister Negative, runsOrganization, FEAST Project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsOrganization Context triple: [Mister Negative, runsOrganization, FEAST Project]
-
A.
campRunBy
Indicates that a particular camp is operated, managed, or administered by a specified person, group, or organization.
-
B.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
C.
testRunOrganizer
Indicates that an entity is responsible for organizing, coordinating, or managing the execution of a specific test run.
-
D.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
-
E.
areOrganizedBy
chosen
Indicates that one entity is responsible for planning, coordinating, or managing the structure or execution of another entity or event.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b27a431c81909c5de3770a594b88 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.