Triple
T35990541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Thymbraeus |
E1040830
|
entity |
| Predicate | hasWorshippers |
P71339
|
FINISHED |
| Object | inhabitants of the Troad |
—
|
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: inhabitants of the Troad | Statement: [Apollo Thymbraeus, hasWorshippers, inhabitants of the Troad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorshippers Context triple: [Apollo Thymbraeus, hasWorshippers, inhabitants of the Troad]
-
A.
worshippers
chosen
Indicates a relationship where one entity shows religious reverence, adoration, or devotion toward another entity as an object of worship.
-
B.
isWorshippedFor
Indicates that one entity is revered or honored by another specifically because of a particular quality, deed, or attribute.
-
C.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
D.
worshipersOffer
Indicates that worshipers present or dedicate offerings to a deity, sacred figure, or religious object.
-
E.
worshipsDeity
Indicates that one entity reveres, honors, or performs religious devotion toward another entity regarded as a deity.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:07 p.m.