Triple
T213959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | military payment certificates |
E4776
|
entity |
| Predicate | userRestriction |
P7913
|
FINISHED |
| Object | intended for use only by U.S. military personnel and authorized civilians |
—
|
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: intended for use only by U.S. military personnel and authorized civilians | Statement: [military payment certificates, userRestriction, intended for use only by U.S. military personnel and authorized civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userRestriction Context triple: [military payment certificates, userRestriction, intended for use only by U.S. military personnel and authorized civilians]
-
A.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
userBase
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
C.
eligibleUses
chosen
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c32ae208190a03d504ef43ea659 |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.