Triple
T11661153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Hoel (DD-533) |
E277120
|
entity |
| Predicate | taskUnitDesignation |
P93772
|
FINISHED |
| Object | Task Unit 77.4.3 |
—
|
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: Task Unit 77.4.3 | Statement: [USS Hoel (DD-533), taskUnitDesignation, Task Unit 77.4.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskUnitDesignation Context triple: [USS Hoel (DD-533), taskUnitDesignation, Task Unit 77.4.3]
-
A.
taskName
Indicates the specific name or label assigned to a task within a process or workflow.
-
B.
designationUnit
Indicates that one entity serves as the unit or standard of measure used to designate, label, or quantify another entity.
-
C.
assignedToUnit
chosen
Indicates that an entity (such as a person, resource, or task) is allocated or designated to a specific unit or organizational subdivision.
-
D.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
E.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d29fdc8190af46b6e2badb1df5 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.