Triple
T35057364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zendan-e Eskandar |
E1011503
|
entity |
| Predicate | hasFunctionAccordingToTradition |
P68064
|
FINISHED |
| Object | prison |
—
|
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: prison | Statement: [Zendan-e Eskandar, hasFunctionAccordingToTradition, prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionAccordingToTradition Context triple: [Zendan-e Eskandar, hasFunctionAccordingToTradition, prison]
-
A.
hasScriptTradition
Indicates that one entity follows, preserves, or is associated with a particular script or writing tradition used for representation or transmission.
-
B.
hasUseInTradition
chosen
Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
-
C.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
-
D.
hasMoveInTradition
Indicates that a particular move or technique is used or recognized within a specific tradition or traditional practice.
-
E.
hasEndTradition
Indicates that an entity marks or represents the concluding part or final phase of a tradition.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.