Triple
T26493894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Order 191 |
E669227
|
entity |
| Predicate | copiesPrepared |
P160796
|
FINISHED |
| Object | multiple copies for subordinate commanders |
—
|
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: multiple copies for subordinate commanders | Statement: [Special Order 191, copiesPrepared, multiple copies for subordinate commanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copiesPrepared Context triple: [Special Order 191, copiesPrepared, multiple copies for subordinate commanders]
-
A.
hasCopy
Indicates that one entity possesses, contains, or maintains a duplicate or instance of another entity.
-
B.
isCopiedBy
Indicates that an entity serves as the source from which another entity is duplicated or reproduced.
-
C.
preparedAt
Indicates the time or place at which something was prepared or made ready.
-
D.
copiesShippedInUS
Indicates that a certain number of copies of an item have been shipped to destinations within the United States.
-
E.
commonlyPreparedFor
Indicates that something is typically made, organized, or arranged in anticipation of a particular event, purpose, or recipient.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61354e6ac8190b5f8d50db9c45d47 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 1:06 a.m.