Triple
T6145103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chez Scheme |
E137054
|
entity |
| Predicate | supportsConcurrency |
P12989
|
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: [Chez Scheme, supportsConcurrency, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsConcurrency Context triple: [Chez Scheme, supportsConcurrency, true]
-
A.
hasConcurrencyConstruct
chosen
Indicates that something includes or utilizes a construct or mechanism for executing multiple operations or tasks concurrently.
-
B.
requiresConcurrenceWith
Indicates that one action, decision, or condition must be agreed upon or approved by another specified party or entity before it can proceed or be valid.
-
C.
heldConcurrentlyWith
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
D.
supportsSuspension
Indicates that one entity provides the necessary structure, strength, or mechanism to hold or keep another entity suspended.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb645508190aea2d77c9de174ba |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.