Triple
T696385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Force |
E13902
|
entity |
| Predicate | readinessLevel |
P11883
|
FINISHED |
| Object | high readiness |
—
|
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: high readiness | Statement: [Regular Force, readinessLevel, high readiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readinessLevel Context triple: [Regular Force, readinessLevel, high readiness]
-
A.
readinessCategory
chosen
Indicates the classification of an entity based on its current level or state of preparedness for a given purpose or activity.
-
B.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
-
C.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
D.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
E.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c5f51c8190acc4915099e4b384 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.