Triple
T6145099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chez Scheme |
E137054
|
entity |
| Predicate | hasGarbageCollectorType |
P16210
|
FINISHED |
| Object | generational |
—
|
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: generational | Statement: [Chez Scheme, hasGarbageCollectorType, generational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarbageCollectorType Context triple: [Chez Scheme, hasGarbageCollectorType, generational]
-
A.
usesGarbageCollectorType
chosen
Indicates that one entity employs or is configured to employ a specific type of garbage collection mechanism or strategy associated with another entity.
-
B.
hasTypeOfSupport
Indicates that one entity provides or is associated with a particular kind or category of support in relation to another entity.
-
C.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
-
D.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
E.
hasTypeOfInstrumentation
Indicates that one entity uses, involves, or is characterized by a particular type of instrumentation.
- 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.