Triple
T35479386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tozama domain |
E1025426
|
entity |
| Predicate | includesNotableExamples |
—
|
GENERATED |
| Object | Satsuma Domain |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNotableExamples Context triple: [tozama domain, includesNotableExamples, Satsuma Domain]
-
A.
notableExampleAt
Indicates that something serves as a prominent or illustrative example of something else in a particular context or location.
-
B.
notableExampleBy
Indicates that something serves as a prominent or illustrative example provided or created by a particular entity.
-
C.
includesExamplesSuchAs
chosen
Indicates that one entity provides specific instances or samples that illustrate or clarify another entity.
-
D.
hasNotableUseExample
Indicates that there exists a particularly significant or illustrative example of how something is used.
-
E.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
- F. None of above.
Provenance (1 batch)
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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.