Triple
T2500043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolaus |
E52441
|
entity |
| Predicate | rewardCriterion |
P216
|
FINISHED |
| Object | good behavior of children |
—
|
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: good behavior of children | Statement: [Nikolaus, rewardCriterion, good behavior of children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardCriterion Context triple: [Nikolaus, rewardCriterion, good behavior of children]
-
A.
rewardSignal
Indicates that one entity provides a signal representing feedback or incentive (such as a reward or penalty) to guide another entity’s behavior or learning process.
-
B.
awardCriteria
chosen
Indicates the standards or conditions used to determine eligibility for receiving an award or recognition.
-
C.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
D.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
E.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1afd86c81909181c4b45d4f8bc5 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.