Triple
T23432645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Apollo at Claros |
E563373
|
entity |
| Predicate | politicalClients |
P152258
|
FINISHED |
| Object | Hellenistic kings |
—
|
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: Hellenistic kings | Statement: [Sanctuary of Apollo at Claros, politicalClients, Hellenistic kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalClients Context triple: [Sanctuary of Apollo at Claros, politicalClients, Hellenistic kings]
-
A.
portraysNotableClient
Indicates that an entity depicts or represents a client who is considered notable or distinguished.
-
B.
organizationRepresentedTo
Indicates that one entity formally acts on behalf of or serves as the representative of an organization in a given context or interaction.
-
C.
plannedClients
Indicates that an entity has scheduled or intended clients associated with it, typically for future services or engagements.
-
D.
legalParties
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
-
E.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d920548190904f80c7c40cba06 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:49 p.m.