Triple
T25879283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 38 |
E651999
|
entity |
| Predicate | siteFunctionContext |
P131774
|
FINISHED |
| Object | ceremonial and funerary precinct of North Acropolis |
—
|
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: ceremonial and funerary precinct of North Acropolis | Statement: [Temple 38, siteFunctionContext, ceremonial and funerary precinct of North Acropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteFunctionContext Context triple: [Temple 38, siteFunctionContext, ceremonial and funerary precinct of North Acropolis]
-
A.
roomFunctionContext
Indicates the contextual role or purpose a room serves within a particular situation, activity, or usage scenario.
-
B.
hasSiteContext
chosen
Indicates that something is associated with, occurs within, or is interpreted relative to a particular site or contextual environment.
-
C.
functionWithinSite
Indicates that one function or activity occurs or is carried out within the spatial or organizational bounds of a particular site.
-
D.
edgeContext
Indicates that a relationship or interaction between two entities occurs within, or is influenced by, a specific contextual setting or surrounding conditions.
-
E.
portFunctionContext
Indicates the functional role or operational context in which a port is used or serves within a system or component.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6033d54948190a52da9e6bef00afa |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:13 a.m.