Triple
T26877054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-ARCOM |
E676779
|
entity |
| Predicate | regulatesWearOnUniform |
P130658
|
FINISHED |
| Object | NATO forces documentation |
—
|
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: NATO forces documentation | Statement: [US-ARCOM, regulatesWearOnUniform, NATO forces documentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesWearOnUniform Context triple: [US-ARCOM, regulatesWearOnUniform, NATO forces documentation]
-
A.
wearsOnUniform
Indicates that an item is part of and is worn as a component of a uniform.
-
B.
mayWearUniform
Indicates that an entity is permitted or authorized to wear a particular uniform in a given context.
-
C.
woreUniformOf
Indicates that one entity was dressed in or used the official uniform associated with another entity (such as an organization, group, or role).
-
D.
wearingRegulatedBy
chosen
Indicates that the act of wearing something is governed, constrained, or directed by a rule, regulation, or authority.
-
E.
wearsUniformSimilarTo
Indicates that one entity wears a uniform that is similar in appearance or style to the uniform worn by another entity.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 5:36 a.m.