Triple
T31886079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AL 288-1 |
E814010
|
entity |
| Predicate | storedInCity |
P48551
|
FINISHED |
| Object | Addis Ababa |
—
|
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: Addis Ababa | Statement: [AL 288-1, storedInCity, Addis Ababa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storedInCity Context triple: [AL 288-1, storedInCity, Addis Ababa]
-
A.
housedInCity
chosen
Indicates that one entity (such as a building, organization, or facility) is located within and contained by a particular city.
-
B.
discoveredInCity
Indicates that something was found, identified, or uncovered within the boundaries of a particular city.
-
C.
deployedInCity
Indicates that an entity has been placed into active use or operation within a particular city.
-
D.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
E.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:57 p.m.