Triple
T34915551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nossob River valley |
E1006988
|
entity |
| Predicate | hasNearestCamp |
P201380
|
FINISHED |
| Object | Nossob Rest Camp |
—
|
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: Nossob Rest Camp | Statement: [Nossob River valley, hasNearestCamp, Nossob Rest Camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearestCamp Context triple: [Nossob River valley, hasNearestCamp, Nossob Rest Camp]
-
A.
hasNearbyPOWCampSite
Indicates that one location is situated close to a prisoner-of-war (POW) camp site.
-
B.
hasNearbyCampAdministeredBy
Indicates that an entity has a nearby camp which is managed or overseen by a specified administrator or organization.
-
C.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
-
D.
hasNearbyTribalLand
Indicates that an entity is located close to or adjacent to land officially recognized as belonging to a tribal nation or indigenous community.
-
E.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
- F. None of above. chosen
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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
| PDg | Predicate description generation | batch_69ffef8003c081909ec2413b4ea08d43 |
completed | May 10, 2026, 2:37 a.m. |
Created at: May 3, 2026, 4 p.m.