Triple
T32967568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Woman from Ephesus |
E843415
|
entity |
| Predicate | likelyFirstPerformancePlace |
P175448
|
FINISHED |
| Object | Greek world |
—
|
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: Greek world | Statement: [The Woman from Ephesus, likelyFirstPerformancePlace, Greek world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyFirstPerformancePlace Context triple: [The Woman from Ephesus, likelyFirstPerformancePlace, Greek world]
-
A.
firstCompletePerformancePlace
Indicates the location where something (such as a work, event, or performance) was first fully performed or completed in its entirety.
-
B.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
C.
firstToAchieve
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
-
D.
firstPerformanceStatus
Indicates the status or outcome of an entity’s initial or debut performance.
-
E.
amongFirstToReach
Indicates that an entity is one of the earliest individuals or groups to arrive at, achieve, or attain a particular place, state, or milestone.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:21 a.m.