Triple
T17560252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rc.d |
E427678
|
entity |
| Predicate | supportsRunLevelConcept |
P127943
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [rc.d, supportsRunLevelConcept, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRunLevelConcept Context triple: [rc.d, supportsRunLevelConcept, false]
-
A.
supportsUserCreatedLevels
Indicates that the system allows and accommodates levels that are created by users rather than only providing built-in levels.
-
B.
supportsPowerLevel
Indicates that one entity is capable of providing or sustaining the required power level for another entity or operation.
-
C.
supportedParadigm
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
-
D.
usesConformanceLevels
Indicates that one entity applies or adheres to defined conformance levels when interacting with or evaluating another entity.
-
E.
supportsTeamLevel
Indicates that one entity provides assistance, resources, or endorsement to a team as a whole rather than to individual members.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562573e48190a19f30fe915a5455 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.