Triple
T30300155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dictionary (Swift) |
E770631
|
entity |
| Predicate | supportsMutation |
P74586
|
FINISHED |
| Object | insertion |
—
|
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: insertion | Statement: [Dictionary (Swift), supportsMutation, insertion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMutation Context triple: [Dictionary (Swift), supportsMutation, insertion]
-
A.
supportedAmendment
Indicates that one entity endorsed, backed, or voted in favor of a particular amendment.
-
B.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
C.
supportsBlock
Indicates that one entity provides structural or functional backing that upholds or stabilizes another entity or block.
-
D.
supportsEditingType
chosen
Indicates that one entity enables or allows another entity to perform or handle a specified type of editing.
-
E.
supportsUndo
Indicates that an action or operation can be reversed or undone after it has been performed.
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:48 p.m.