Triple
T30836819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schoelcher Library |
E785385
|
entity |
| Predicate | hasMetalFramework |
P154675
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Schoelcher Library, hasMetalFramework, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetalFramework Context triple: [Schoelcher Library, hasMetalFramework, yes]
-
A.
supportsMetalVersion
Indicates that one entity is compatible with or able to operate using a specified version of the Metal graphics framework.
-
B.
coreMetal
chosen
Indicates that one entity serves as the primary or central metal component within another entity or structure.
-
C.
hasFrameworkInstrument
Indicates that one entity uses or is associated with a specific framework as the instrument or means for performing an action or achieving a result.
-
D.
hasFrameworkType
Indicates that an entity is associated with or classified by a specific type or category of framework.
-
E.
hasDistinctiveFrameworkWith
Indicates that one entity possesses a unique or distinguishing structural framework in relation to 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 29, 2026, 8:45 p.m.