Triple
T24138430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saro people |
E598154
|
entity |
| Predicate | primaryOriginLocation |
P56832
|
FINISHED |
| Object | Sierra Leone |
—
|
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: Sierra Leone | Statement: [Saro people, primaryOriginLocation, Sierra Leone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOriginLocation Context triple: [Saro people, primaryOriginLocation, Sierra Leone]
-
A.
primaryOriginState
Indicates the state that serves as the main or original source location associated with an entity.
-
B.
physicalOrigin
chosen
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
C.
originalLocationType
Indicates the type or category of the place where something was originally located or came from.
-
D.
originalLocationStatus
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
E.
originLocality
Indicates the specific locality or place where an entity (typically a specimen or item) originally came from or was collected.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.