Triple
T3201042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-bar theory |
E67050
|
entity |
| Predicate | relatesAdjunctTo |
P34778
|
FINISHED |
| Object | recursive modifier position |
—
|
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: recursive modifier position | Statement: [X-bar theory, relatesAdjunctTo, recursive modifier position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesAdjunctTo Context triple: [X-bar theory, relatesAdjunctTo, recursive modifier position]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
E.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9aedef08190824bdf508f85f06f |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.