Triple
T29824533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rod |
E757344
|
entity |
| Predicate | functionWithRozhanitsy |
P160683
|
FINISHED |
| Object | determining fate of newborns |
—
|
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: determining fate of newborns | Statement: [Rod, functionWithRozhanitsy, determining fate of newborns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionWithRozhanitsy Context triple: [Rod, functionWithRozhanitsy, determining fate of newborns]
-
A.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
B.
functionInRecital
Indicates that an entity performs or participates in a musical or artistic function within a recital event.
-
C.
rukus
Indicates that an entity is associated with or participates in a disturbance, commotion, or noisy disruptive event involving another entity.
-
D.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
E.
functionInMagic
chosen
Indicates that an entity serves a specific role or performs a particular function within a magical system, process, or context.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 5:31 p.m.