Triple
T35921531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaon of Sura |
E1038898
|
entity |
| Predicate | endOfProminence |
P48547
|
FINISHED |
| Object | around 11th century |
—
|
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: around 11th century | Statement: [Gaon of Sura, endOfProminence, around 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfProminence Context triple: [Gaon of Sura, endOfProminence, around 11th century]
-
A.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
B.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
-
C.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
notableEnding
Indicates that an entity concludes or finishes in a way that is remarkable, memorable, or otherwise noteworthy.
-
E.
phoneticEnd
Indicates that two linguistic elements share the same or similar ending sound in their pronunciation.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:07 p.m.