Triple
T35739440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kemal |
E1032990
|
entity |
| Predicate | collectsObjectsBelongingTo |
P87654
|
FINISHED |
| Object | Füsun |
—
|
NE NERFINISHED |
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: Füsun | Statement: [Kemal, collectsObjectsBelongingTo, Füsun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsObjectsBelongingTo Context triple: [Kemal, collectsObjectsBelongingTo, Füsun]
-
A.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
B.
collectionBy
chosen
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
C.
bringsObjectFrom
Indicates that an agent transports or carries an object from a specified source location to another context or entity.
-
D.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
-
E.
coreCollectionOf
Indicates that one entity serves as the primary or central collection that another entity belongs to or is grouped within.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:05 p.m.