Triple
T17618870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRAF Stage II |
E429655
|
entity |
| Predicate | hasActivationLevel |
P127909
|
FINISHED |
| Object | intermediate |
—
|
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: intermediate | Statement: [CRAF Stage II, hasActivationLevel, intermediate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivationLevel Context triple: [CRAF Stage II, hasActivationLevel, intermediate]
-
A.
activationLevel
chosen
Indicates the degree or intensity to which something is currently active, engaged, or functioning within a given context.
-
B.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
C.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
D.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
E.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3489dc8190a619c58025dbb250 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.