Triple
T5468845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aigai |
E122779
|
entity |
| Predicate | continuedFunctionAfterCapitalMove |
P37801
|
FINISHED |
| Object | royal burial center |
—
|
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: royal burial center | Statement: [Aigai, continuedFunctionAfterCapitalMove, royal burial center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedFunctionAfterCapitalMove Context triple: [Aigai, continuedFunctionAfterCapitalMove, royal burial center]
-
A.
laterFunction
Indicates that one function or event occurs after another in time.
-
B.
focusAfterTransition
chosen
Indicates that focus is moved to a specific element or area after a transition or state change has completed.
-
C.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
D.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
E.
capitalMovedFrom
Indicates that a capital city was relocated from one place (the source) to another (the destination).
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.