Triple
T18791012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Reserve Technician |
E459512
|
entity |
| Predicate | readinessRole |
P11687
|
FINISHED |
| Object | monitor and report unit readiness status |
—
|
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: monitor and report unit readiness status | Statement: [Air Reserve Technician, readinessRole, monitor and report unit readiness status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readinessRole Context triple: [Air Reserve Technician, readinessRole, monitor and report unit readiness status]
-
A.
configurationRole
Indicates the role or function an entity assumes within a particular configuration or setup.
-
B.
harborRole
Indicates that an entity serves in a particular capacity, function, or role within a specified context or relationship.
-
C.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
roleInCluster
Indicates the specific function or position an entity holds within a defined group or cluster of related entities.
-
E.
lambdaRole
Indicates that one entity functions as a lambda expression or anonymous functional role in relation to another entity within a logical or computational structure.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978599008190aaceaff1b1e0a2c7 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.