Triple
T20703952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F401 |
E508850
|
entity |
| Predicate | applicationStatus |
P141163
|
FINISHED |
| Object | intended for military use |
—
|
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 military use | Statement: [F401, applicationStatus, intended for military use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationStatus Context triple: [F401, applicationStatus, intended for military use]
-
A.
applicantState
Indicates the current status or condition assigned to an applicant within a process or system.
-
B.
applicantStates
Indicates that an applicant explicitly declares or asserts a particular fact, condition, or piece of information.
-
C.
appliedFor
Indicates that an entity has submitted a request or application to another entity for a position, service, benefit, or opportunity.
-
D.
applicantIn
Indicates that a person or entity is serving as an applicant within a particular context, process, or organization.
-
E.
applicationProcessIncludes
Indicates that an application process contains or encompasses a specific step, component, or sub-process as part of its overall workflow.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18dbda081908217dcb61cbf7ba4 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:13 p.m.