Triple
T14786316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebat Bet Gurage |
E347533
|
entity |
| Predicate | secondaryLocationType |
P26823
|
FINISHED |
| Object | small towns |
—
|
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: small towns | Statement: [Sebat Bet Gurage, secondaryLocationType, small towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryLocationType Context triple: [Sebat Bet Gurage, secondaryLocationType, small towns]
-
A.
secondarySite
Indicates that one entity serves as an additional or subordinate location associated with another primary site.
-
B.
secondaryHeadquartersLocation
Indicates the location where an organization maintains a secondary (non-primary) headquarters.
-
C.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
D.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
E.
secondaryGeographicFocus
chosen
Indicates a secondary or less primary geographic area that is also a focus or target of the entity’s activities, influence, or relevance.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa083e481908336d58d026eec32 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.