Triple
T19737892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEED AP O+M |
E474034
|
entity |
| Predicate | validityRequires |
P90349
|
FINISHED |
| Object | continuing education |
—
|
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: continuing education | Statement: [LEED AP O+M, validityRequires, continuing education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validityRequires Context triple: [LEED AP O+M, validityRequires, continuing education]
-
A.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
B.
requiresValidationAt
Indicates that an entity must undergo validation at a specific point, condition, or stage in a process.
-
C.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
D.
validityRegime
Indicates the set of conditions, rules, or context under which something (such as a statement, document, or status) is considered valid or in force.
-
E.
requiredTo
chosen
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515ea688819097b6838e6a3b3d4a |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.