Triple
T8102107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niko Tinbergen |
E189137
|
entity |
| Predicate | fourQuestionsComponent |
P80469
|
FINISHED |
| Object | causation (mechanism) |
—
|
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: causation (mechanism) | Statement: [Niko Tinbergen, fourQuestionsComponent, causation (mechanism)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourQuestionsComponent Context triple: [Niko Tinbergen, fourQuestionsComponent, causation (mechanism)]
-
A.
questionForm
Indicates that one entity is expressed or structured in the form of a question directed toward another entity or context.
-
B.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
C.
canAnswerQuestions
Indicates that an entity has the ability or capacity to respond correctly or appropriately to questions.
-
D.
guidingQuestionOf
Indicates that one item serves as a guiding or central question that frames, directs, or structures another item (such as a discussion, activity, or work).
-
E.
numberOfQuestions
Indicates the total count of questions associated with or contained in a given entity or context.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42bd91408190880293dfdce8bef7 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:31 p.m.