Triple
T34588961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazel |
E888122
|
entity |
| Predicate | reasonPursued |
P19457
|
FINISHED |
| Object | illegal hybrid child in the context of the war |
—
|
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: illegal hybrid child in the context of the war | Statement: [Hazel, reasonPursued, illegal hybrid child in the context of the war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonPursued Context triple: [Hazel, reasonPursued, illegal hybrid child in the context of the war]
-
A.
motivationFor
chosen
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
B.
reasonForAcquisition
Indicates the underlying purpose, motive, or justification for which one entity acquires another entity or asset.
-
C.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
reasonForPledge
Indicates the motivation or justification behind making a particular pledge or commitment.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 1, 2026, 2:03 a.m.