Triple
T4684973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabala |
E103897
|
entity |
| Predicate | presentDayStatus |
P28747
|
FINISHED |
| Object | inhabited city |
—
|
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: inhabited city | Statement: [Jabala, presentDayStatus, inhabited city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayStatus Context triple: [Jabala, presentDayStatus, inhabited city]
-
A.
presentDayControl
Indicates that one entity currently holds authority, governance, or control over another entity in the present day.
-
B.
statusAtDay
Indicates the specific status or condition an entity has on a given calendar day.
-
C.
presentDayCenter
Indicates that an entity currently serves as the central or primary focal point (e.g., administrative, cultural, or functional center) of another entity in the present day.
-
D.
presentDayProvince
Indicates that one entity is the present-day administrative province in which the other entity is currently located or to which it now belongs.
-
E.
modernStatus
chosen
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.