Triple
T27615620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boehm-Demers-Weiser conservative GC |
E700430
|
entity |
| Predicate | collectionStrategy |
P152671
|
FINISHED |
| Object | mark-and-sweep |
—
|
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: mark-and-sweep | Statement: [Boehm-Demers-Weiser conservative GC, collectionStrategy, mark-and-sweep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionStrategy Context triple: [Boehm-Demers-Weiser conservative GC, collectionStrategy, mark-and-sweep]
-
A.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
B.
collectionScope
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
C.
collectionMethods
chosen
Indicates the ways or procedures by which something is gathered, obtained, or collected.
-
D.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
-
E.
collectionPolicy
Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 2:12 p.m.