Triple
T33072631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petun |
E846272
|
entity |
| Predicate | dispersedIn |
P175773
|
FINISHED |
| Object | mid-17th century |
—
|
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: mid-17th century | Statement: [Petun, dispersedIn, mid-17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dispersedIn Context triple: [Petun, dispersedIn, mid-17th century]
-
A.
dispersedBy
Indicates that one entity is spread, scattered, or distributed as a result of the actions or influence of another entity.
-
B.
dispersingElement
Indicates that one entity causes another entity to spread out or scatter from a concentrated state into a wider area or among multiple parts.
-
C.
dispersion
Indicates the degree to which items in a set are spread out or scattered relative to one another.
-
D.
distributedThrough
Indicates that something is supplied, delivered, or made available to others by means of a particular channel, intermediary, or distribution method.
-
E.
distributedWith
Indicates that one entity is supplied, packaged, or made available together with another entity as part of the same distribution.
- F. None of above. chosen
Provenance (4 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:25 a.m.