Triple
T3263445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herod Philip |
E68466
|
entity |
| Predicate | realmWithin |
P46950
|
FINISHED |
| Object | Roman client kingdom of Judea |
—
|
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: Roman client kingdom of Judea | Statement: [Herod Philip, realmWithin, Roman client kingdom of Judea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmWithin Context triple: [Herod Philip, realmWithin, Roman client kingdom of Judea]
-
A.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
B.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
C.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
D.
coreTerritoryAround
Indicates that one entity serves as the central or primary territory surrounding or enclosing another entity.
-
E.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafaa35e48190b894ca41dd65932b |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.