Triple
T30122666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRDC-ESP |
E765599
|
entity |
| Predicate | isHighReadiness |
P168467
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NRDC-ESP, isHighReadiness, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighReadiness Context triple: [NRDC-ESP, isHighReadiness, true]
-
A.
hasReadinessRequirement
Indicates that something is subject to a specific condition or level of preparedness that must be met before it can proceed or be considered acceptable.
-
B.
readinessCategory
Indicates the classification of an entity based on its current level or state of preparedness for a given purpose or activity.
-
C.
isProductionReady
Indicates that something has met all necessary quality, stability, and performance criteria to be safely deployed and used in a live production environment.
-
D.
declaresReadinessFor
Indicates that an entity formally states or signals that it is prepared to perform a task, assume a role, or proceed with an action.
-
E.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
- F. None of above. chosen
Provenance (4 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67debf2308190b955958a85154a24 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:13 p.m.