Triple
T10275259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sayil |
E240947
|
entity |
| Predicate | primaryFunctionInAntiquity |
P93071
|
FINISHED |
| Object | regional administrative 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: regional administrative center | Statement: [Sayil, primaryFunctionInAntiquity, regional administrative center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionInAntiquity Context triple: [Sayil, primaryFunctionInAntiquity, regional administrative center]
-
A.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
-
B.
primaryFunctionOfInscriptions
Indicates that the specified function is the main or principal purpose served by the inscriptions in question.
-
C.
primaryFunctionMedieval
Indicates the main role or purpose an entity served within a medieval context (e.g., its primary function in medieval society, technology, or institutions).
-
D.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
E.
primaryFunctionInPractice
Indicates that an entity serves as the main or most important function or role within a given practical context or real-world usage.
- F. None of above. chosen
Provenance (4 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d28b6cd4819084a7a5c1893b5ad8 |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d285812c8190ab910dc85c53eebf |
completed | April 7, 2026, 9:46 a.m. |
Created at: April 6, 2026, 11:37 a.m.