Triple
T30300145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dictionary (Swift) |
E770631
|
entity |
| Predicate | defaultImplementationDetail |
P19961
|
FINISHED |
| Object | hash table based |
—
|
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: hash table based | Statement: [Dictionary (Swift), defaultImplementationDetail, hash table based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultImplementationDetail Context triple: [Dictionary (Swift), defaultImplementationDetail, hash table based]
-
A.
hasImplementationDetail
chosen
Indicates that one entity specifies or contains a concrete implementation detail or internal mechanism related to another entity.
-
B.
defaultImplementationSource
Indicates the origin or provider from which a default implementation of something is derived or supplied.
-
C.
hidesImplementationDetail
Indicates that one entity conceals or abstracts away the internal workings or specifics of another entity from external view or use.
-
D.
defaultImplementationFor
Indicates that one entity serves as the standard or fallback implementation used when no more specific implementation is provided for another entity.
-
E.
exampleImplementation
Indicates that one entity serves as a concrete, illustrative implementation or instance of another, more general concept, design, or specification.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 7:48 p.m.