Triple
T25940996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Khe, South Vietnam |
E653697
|
entity |
| Predicate | CampRadcliffFunction |
P136644
|
FINISHED |
| Object | logistics and support complex |
—
|
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: logistics and support complex | Statement: [An Khe, South Vietnam, CampRadcliffFunction, logistics and support complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CampRadcliffFunction Context triple: [An Khe, South Vietnam, CampRadcliffFunction, logistics and support complex]
-
A.
campFunction
chosen
Indicates that an entity serves a particular role, purpose, or function within the context of a camp.
-
B.
functionInClimb
Indicates that an entity serves a specific role or purpose within a climbing activity or ascent.
-
C.
campSystem
Indicates a relationship where an entity is part of, managed by, or associated with a particular camp system or organized camp structure.
-
D.
campLocation
Indicates the place or area where a camp is set up or located.
-
E.
castleFunction
Indicates the primary role, purpose, or use that a castle serves (e.g., defense, residence, administration, or symbolism).
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045dedb4819087530b823c036d51 |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:40 a.m.