Triple
T28740768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Artemis near Phigaleia |
E731231
|
entity |
| Predicate | likelyHad |
P159732
|
FINISHED |
| Object | altar |
—
|
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: altar | Statement: [Sanctuary of Artemis near Phigaleia, likelyHad, altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyHad Context triple: [Sanctuary of Artemis near Phigaleia, likelyHad, altar]
-
A.
likelyStatus
Indicates the probable or expected state or condition of an entity based on available information or inference.
-
B.
possiblyBy
Indicates that an action, creation, or effect may have been caused or produced by a particular entity, but this attribution is uncertain or not definitively established.
-
C.
believedToHave
chosen
Indicates that one entity is thought or assumed, but not confirmed, to possess or exhibit another entity or property.
-
D.
likelyBehavior
Indicates the behavior or action that an entity is expected or predicted to exhibit under given circumstances.
-
E.
almostCaused
Indicates that one entity’s actions or state came close to causing an effect or event involving another entity, but the outcome ultimately did not occur.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 6:02 a.m.