Triple
T28792549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multiple Spell-Out theory |
E726992
|
entity |
| Predicate | usedInAnalysisOf |
P78157
|
FINISHED |
| Object | wh-movement |
—
|
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-movement | Statement: [Multiple Spell-Out theory, usedInAnalysisOf, wh-movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAnalysisOf Context triple: [Multiple Spell-Out theory, usedInAnalysisOf, wh-movement]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
oftenAnalyzedIn
chosen
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
C.
usedInStatistic
Indicates that something (such as a value, measure, or data item) is employed as part of the calculation or presentation of a particular statistic.
-
D.
usedInDescriptionOf
Indicates that one entity is employed as part of the descriptive content or explanation of another entity.
-
E.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 6:24 a.m.