Triple
T18373474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES |
E446246
|
entity |
| Predicate | hasAssignmentStatus |
P50846
|
FINISHED |
| Object | currently assigned |
—
|
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: currently assigned | Statement: [ES, hasAssignmentStatus, currently assigned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssignmentStatus Context triple: [ES, hasAssignmentStatus, currently assigned]
-
A.
hasOfficialAssignment
Indicates that an entity has been formally designated or tasked with a specific role, duty, or responsibility by an authorized body.
-
B.
assignedToState
chosen
Indicates that something has been allocated or designated to a particular state or status.
-
C.
hasAssigningAuthority
Indicates that one entity serves as the official source or authority responsible for assigning or issuing identifiers, codes, or designations to another entity.
-
D.
hasWorkStatus
Indicates the current employment or occupational state associated with an entity, such as whether it is active, inactive, or in a specific work condition.
-
E.
hasDraftOrAssignmentSystem
Indicates that an entity possesses or is associated with a system for managing drafts or assignments.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e517561edc8190b5d2834707ab662b |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.