Triple
T3094338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principles and Parameters Theory |
E64556
|
entity |
| Predicate | exampleParameter |
P4452
|
FINISHED |
| Object | head-directionality parameter |
—
|
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: head-directionality parameter | Statement: [Principles and Parameters Theory, exampleParameter, head-directionality parameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleParameter Context triple: [Principles and Parameters Theory, exampleParameter, head-directionality parameter]
-
A.
parameter
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
hasParameter
chosen
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
-
C.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
-
D.
commandOption
Indicates that one entity is a configurable command-line option or parameter associated with another command or executable.
-
E.
toolUseExamples
Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada239a8c88190a746892b56ee7e02 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.