Triple
T14829396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Stoa |
E348656
|
entity |
| Predicate | governingBodyAssociated |
P24141
|
FINISHED |
| Object | Athenian polis |
—
|
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: Athenian polis | Statement: [Royal Stoa, governingBodyAssociated, Athenian polis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingBodyAssociated Context triple: [Royal Stoa, governingBodyAssociated, Athenian polis]
-
A.
governingBodyOrSupport
Indicates that one entity serves as the governing authority for, or provides official support to, another entity.
-
B.
governingBody2
chosen
Indicates that an entity serves as the official authority or administrative body responsible for overseeing, managing, or regulating another entity.
-
C.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
D.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
-
E.
governingBodyInvolvement
Indicates the extent or manner in which a governing body participates in, oversees, or influences a particular activity, decision, or entity.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0737d4c8190a49bf6b013da208c |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.