Triple
T13987938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subjacency |
E336489
|
entity |
| Predicate | examplePhenomenon |
P112065
|
FINISHED |
| Object | wh-extraction from embedded clauses |
—
|
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: wh-extraction from embedded clauses | Statement: [Subjacency, examplePhenomenon, wh-extraction from embedded clauses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examplePhenomenon Context triple: [Subjacency, examplePhenomenon, wh-extraction from embedded clauses]
-
A.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
B.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
C.
demonstratedPhenomenon
Indicates that an entity has shown, exhibited, or provided evidence for the occurrence of a particular phenomenon.
-
D.
affectsPhenomenon
Indicates that one phenomenon produces an influence or change on another phenomenon.
-
E.
allegedPhenomenon
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea537408190bb9d35963886803f |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:18 p.m.