Triple
T25352214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribes of Israel |
E635716
|
entity |
| Predicate | hasCapitalInSomePeriods |
P29979
|
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: [Tribes of Israel, hasCapitalInSomePeriods, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalInSomePeriods Context triple: [Tribes of Israel, hasCapitalInSomePeriods, Jerusalem]
-
A.
hasLaterCapital
Indicates that one entity’s designation or establishment as a capital city occurred later in time than that of another entity.
-
B.
hasCapitalDuringProcess
Indicates that an entity possesses or controls capital (financial or resource assets) throughout the duration of a specified process or activity.
-
C.
hasTraditionalCapital
Indicates that an entity serves or is recognized as the traditional or historical capital of another entity.
-
D.
hasCapitalDuringColonialPeriod
Indicates that a specified location served as the capital of a political entity during its colonial period.
-
E.
servedAsCapitalDuring
chosen
Indicates that a place functioned as the official capital of a political entity during a specified time period.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:34 p.m.