Triple

T32872813
Position Surface form Disambiguated ID Type / Status
Subject Bouleuterion E840835 entity
Predicate adjacentTo P224 FINISHED
Object Metroon of Athens
The Metroon of Athens was an ancient civic building in the Athenian Agora that housed the archives and a temple of the mother goddess, serving as both a religious and administrative center.
E2025440 NE 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: Metroon of Athens | Statement: [Bouleuterion, adjacentTo, Metroon of Athens]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Metroon of Athens
Triple: [Bouleuterion, adjacentTo, Metroon of Athens]
Generated description
The Metroon of Athens was an ancient civic building in the Athenian Agora that housed the archives and a temple of the mother goddess, serving as both a religious and administrative center.

Provenance (5 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_69f349436ee88190b72ee12d0f3f508e completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6cfe90a4c81909662075cd8a8c715 completed May 3, 2026, 4:32 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34bd1732f0819089b4fa6eb62c7769 completed June 19, 2026, 3:52 a.m.
NEDg Description generation batch_6a34bda4d1308190932b182fc3daee1f completed June 19, 2026, 3:55 a.m.
NED2 Entity disambiguation (via description) batch_6a34be49d2c0819089cb85ac34fa49ca completed June 19, 2026, 3:58 a.m.
Created at: May 1, 2026, 1:17 a.m.