Triple
T25964720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bending Spoons |
E645634
|
entity |
| Predicate | acquisitionOfEvernote |
P81864
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Bending Spoons, acquisitionOfEvernote, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfEvernote Context triple: [Bending Spoons, acquisitionOfEvernote, 2023]
-
A.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
B.
sharesNotabilityWith
Indicates that two entities are notable or recognized for the same or closely related reason, characteristic, or achievement.
-
C.
acquiredWith
chosen
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
-
D.
notableApp
Indicates that an application is recognized as significant, prominent, or noteworthy in some context.
-
E.
notableClient
Indicates that one entity serves as a prominent or distinguished client of 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c8ef408190bfd4571fb262372b |
completed | May 2, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:48 a.m.