Triple
T34278563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korengal Valley |
E879528
|
entity |
| Predicate | notableOutpost |
P701
|
FINISHED |
| Object | Outpost Restrepo |
E699309
|
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: Outpost Restrepo | Statement: [Korengal Valley, notableOutpost, Outpost Restrepo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOutpost Context triple: [Korengal Valley, notableOutpost, Outpost Restrepo]
-
A.
notableEnclave
Indicates that one place is a distinct, noteworthy enclave located within or surrounded by another area or community.
-
B.
notableOutlet
Indicates that an entity is a prominent or widely recognized source, channel, or venue through which another entity is presented, distributed, or publicized.
-
C.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
notableCamp
chosen
Indicates that an entity is a camp that is notable or significant in some recognized way (e.g., historically, culturally, or by prominence).
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36e629ba608190b3289611cf455612 |
completed | June 20, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.