Triple
T23955998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaddachauki |
E603788
|
entity |
| Predicate | hasImmigrationOffice |
P7852
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gaddachauki, hasImmigrationOffice, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmigrationOffice Context triple: [Gaddachauki, hasImmigrationOffice, yes]
-
A.
immigrationAuthority
Indicates that an entity has official power or responsibility to regulate, control, or make decisions about immigration-related matters concerning another entity.
-
B.
hasAssociatedOffice
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
-
C.
hasConsularEntranceOn
Indicates that a consular facility or office has an entrance located on a specified street, side, or access point.
-
D.
closedAsImmigrationStation
Indicates that an entity ceased operating in its role as an immigration station.
-
E.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d6d7688190bedf55dda8e72b2b |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:22 p.m.