Triple
T28650607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Haystack in the Floods |
E725182
|
entity |
| Predicate | featuresExecution |
P197513
|
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 Haystack in the Floods, featuresExecution, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresExecution Context triple: [The Haystack in the Floods, featuresExecution, true]
-
A.
featuresExperiment
Indicates that an entity is involved in, or is the subject of, a specific experimental setup, test, or trial.
-
B.
featuresAbility
Indicates that one entity possesses, includes, or provides a particular ability or capability associated with another entity.
-
C.
featuresOrchestrationBy
Indicates that something (such as a work, event, or performance) is characterized by or includes orchestration carried out by a particular agent or entity.
-
D.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
E.
featuresPerformanceBy
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69fe991abc6c81908edbb98d61c9ca73 |
completed | May 9, 2026, 2:16 a.m. |
Created at: April 28, 2026, 4:51 a.m.