Triple
T30680161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herodian tetrarchy |
E781029
|
entity |
| Predicate | hasCapitalInDivision |
P204
|
FINISHED |
| Object | Jerusalem |
—
|
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: Jerusalem | Statement: [Herodian tetrarchy, hasCapitalInDivision, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalInDivision Context triple: [Herodian tetrarchy, hasCapitalInDivision, Jerusalem]
-
A.
hasCapitalUT
Indicates that a political or administrative entity has a specific city as its capital, with the relation defined using untyped (UT) resources.
-
B.
hasCapital
chosen
Indicates that a place or political entity has a specific city designated as its capital.
-
C.
hasCapitalDistrictStatus
Indicates that an administrative region holds the official status of being a capital district within a country or larger jurisdiction.
-
D.
containsCapitalOf
Indicates that one location geographically includes the city that serves as the capital of another region or entity.
-
E.
hasCapitalSee
Indicates that one entity (typically a country, state, or organization) possesses a designated capital city or principal seat of authority in the other entity.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: April 29, 2026, 8:32 p.m.