Triple
T28690469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp 5 |
E729265
|
entity |
| Predicate | relativeToCamp6 |
P202176
|
FINISHED |
| Object | similar high-security role to Camp 6 |
—
|
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: similar high-security role to Camp 6 | Statement: [Camp 5, relativeToCamp6, similar high-security role to Camp 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToCamp6 Context triple: [Camp 5, relativeToCamp6, similar high-security role to Camp 6]
-
A.
relativeToCamp4
Indicates a spatial or contextual relationship defined with respect to the location or reference frame of Camp 4.
-
B.
hasNearestCamp
Indicates that one entity is the closest camp in distance or proximity to another specified entity.
-
C.
baseCampFor
Indicates that one location serves as the primary staging or support site for activities conducted in another location.
-
D.
tribalCampPosition
Indicates the spatial or geographic position of a tribal camp relative to other locations or features.
-
E.
campPositionInWilderness
Indicates the spatial location or placement of a camp within a wilderness area.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
| PDg | Predicate description generation | batch_6a005d86d6e481909e9f6ae81568cfb8 |
completed | May 10, 2026, 10:27 a.m. |
Created at: April 28, 2026, 5:35 a.m.