Triple
T27734955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.IO.PathTooLongException |
E697507
|
entity |
| Predicate | isCheckedAtRuntime |
P163122
|
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: [System.IO.PathTooLongException, isCheckedAtRuntime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCheckedAtRuntime Context triple: [System.IO.PathTooLongException, isCheckedAtRuntime, true]
-
A.
checkedDuring
Indicates that an entity was examined, inspected, or verified at a specific time or during a particular event or process.
-
B.
isCheckedException
Indicates that an exception must be declared or handled explicitly at compile time, as opposed to being unchecked.
-
C.
isRuntimeEnforced
chosen
Indicates that a rule, constraint, or condition is actively checked and enforced during program execution rather than at compile time or design time.
-
D.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
E.
hasWorkRuntimeAppearedIn
Indicates that a particular work runtime has been featured or included in a specified context, such as a release, edition, or presentation.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:12 p.m.