Triple
T34330077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Patrick Henry, Virginia |
E880978
|
entity |
| Predicate | processedFor |
P179118
|
FINISHED |
| Object | overseas deployment |
—
|
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: overseas deployment | Statement: [Camp Patrick Henry, Virginia, processedFor, overseas deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processedFor Context triple: [Camp Patrick Henry, Virginia, processedFor, overseas deployment]
-
A.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
B.
processed
Indicates that an entity has undergone some form of treatment, handling, or transformation, typically changing its state or condition from an original form.
-
C.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
D.
isProcessedBy
Indicates that an entity undergoes some form of handling, transformation, or treatment performed by another entity or agent.
-
E.
preparedWithin
Indicates that an item or outcome is created, completed, or made ready within a specified time frame or duration.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:58 a.m.