Triple
T30234658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guere-Krahn |
E768726
|
entity |
| Predicate | primarilyFoundIn |
P130611
|
FINISHED |
| Object | Liberia |
E6007
|
NE 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: Liberia | Statement: [Guere-Krahn, primarilyFoundIn, Liberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarilyFoundIn Context triple: [Guere-Krahn, primarilyFoundIn, Liberia]
-
A.
isCommonlyFoundAt
Indicates that an entity typically or frequently occurs, appears, or is present in a particular location or context.
-
B.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
C.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
D.
mainlyObservedIn
chosen
Indicates that something occurs, appears, or is found predominantly within a particular context, location, group, or condition.
-
E.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
- F. None of above.
Provenance (4 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01e27bb77c8190a7686b77a524f177 |
completed | May 11, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27642e1ae88190a92ddee08434159b |
completed | June 9, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_6a01da2614788190b31db15539f5ba58 |
completed | May 11, 2026, 1:31 p.m. |
Created at: April 29, 2026, 7:37 p.m.