Triple
T15569970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colégio de São Pedro (Coimbra) |
E374212
|
entity |
| Predicate | hasFunctionInThePresent |
P61430
|
FINISHED |
| Object | historic site |
—
|
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: historic site | Statement: [Colégio de São Pedro (Coimbra), hasFunctionInThePresent, historic site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInThePresent Context triple: [Colégio de São Pedro (Coimbra), hasFunctionInThePresent, historic site]
-
A.
hasFunctionInPresent
chosen
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
B.
hasFunctionInWork
Indicates that an entity serves a specific role or performs a particular function within a given work (such as a creative, scholarly, or technical work).
-
C.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
D.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
E.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e1de0488190b3639fc25f79d343 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.