Triple
T3201041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-bar theory |
E67050
|
entity |
| Predicate | relatesComplementTo |
P46109
|
FINISHED |
| Object | sister of head |
—
|
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: sister of head | Statement: [X-bar theory, relatesComplementTo, sister of head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesComplementTo Context triple: [X-bar theory, relatesComplementTo, sister of head]
-
A.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
B.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
D.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
E.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
- 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_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. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.