Triple
T8765373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M81 Woodland pattern |
E208325
|
entity |
| Predicate | widelyCopiedBy |
P78822
|
FINISHED |
| Object | foreign militaries |
—
|
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: foreign militaries | Statement: [M81 Woodland pattern, widelyCopiedBy, foreign militaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyCopiedBy Context triple: [M81 Woodland pattern, widelyCopiedBy, foreign militaries]
-
A.
isCopiedBy
chosen
Indicates that an entity serves as the source from which another entity is duplicated or reproduced.
-
B.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
C.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
D.
widelyCoveredBy
Indicates that something (such as an event, topic, or issue) receives extensive attention or reporting from many media outlets or information sources.
-
E.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ee850b88190a0294bcbe4045aa3 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.