Triple
T24024992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manaen |
E594927
|
entity |
| Predicate | broughtUpWith |
P154908
|
FINISHED |
| Object | Herod the tetrarch |
—
|
NE NERFINISHED |
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: Herod the tetrarch | Statement: [Manaen, broughtUpWith, Herod the tetrarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtUpWith Context triple: [Manaen, broughtUpWith, Herod the tetrarch]
-
A.
upbringing
Indicates the relationship in which one entity raises, nurtures, and shapes the early development and values of another.
-
B.
raisedBy
Indicates that one entity has been brought up, nurtured, or reared under the care, guidance, or authority of another entity.
-
C.
upbringingControlledBy
Indicates that one entity has authority over and directs the upbringing or child-rearing process of another entity.
-
D.
raisedAs
Indicates that one entity was brought up, nurtured, or reared in the role, identity, or condition specified by another entity.
-
E.
sonRaisedIn
Indicates that a son spent his childhood or formative years being brought up in a particular place or environment.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d769f7248190ae145218fb0e8bbd |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:53 p.m.