Triple
T18663229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Service |
E456255
|
entity |
| Predicate | statusChangeTo |
P35872
|
FINISHED |
| Object | reserve 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: reserve status | Statement: [Active Service, statusChangeTo, reserve status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusChangeTo Context triple: [Active Service, statusChangeTo, reserve status]
-
A.
statusChange
chosen
Indicates a transition in an entity’s state or condition from one status to another over time.
-
B.
statusChangeRule
Indicates a rule or condition that governs how and when an entity’s status is allowed to change from one state to another.
-
C.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508c0d088190bef46fb3a3001f10 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.