Triple
T28265252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comarnic |
E712683
|
entity |
| Predicate | governingBody |
P46
|
FINISHED |
| Object |
Comarnic Town Hall
Comarnic Town Hall is the main municipal administrative building and local government headquarters for the town of Comarnic in Romania.
|
E1810359
|
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: Comarnic Town Hall | Statement: [Comarnic, governingBody, Comarnic Town Hall]
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: Comarnic Town Hall Triple: [Comarnic, governingBody, Comarnic Town Hall]
Generated description
Comarnic Town Hall is the main municipal administrative building and local government headquarters for the town of Comarnic in Romania.
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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6441d0e5c8190ba32a2107c3f368a |
completed | May 2, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1607194e5481908a34d0369576827c |
completed | May 26, 2026, 8:48 p.m. |
| NEDg | Description generation | batch_6a16129abae08190b2d7e38652b13d98 |
completed | May 26, 2026, 9:37 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a16130f16788190b11d1201c3de47d0 |
completed | May 26, 2026, 9:39 p.m. |
Created at: April 27, 2026, 11:14 p.m.