Triple
T35875114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Architect of the Holy Land |
E1037335
|
entity |
| Predicate | appliedAsHonorTo |
P154736
|
FINISHED |
| Object | Antonio Barluzzi |
—
|
NE NERFINISHED |
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: Antonio Barluzzi | Statement: [Architect of the Holy Land, appliedAsHonorTo, Antonio Barluzzi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedAsHonorTo Context triple: [Architect of the Holy Land, appliedAsHonorTo, Antonio Barluzzi]
-
A.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
B.
grantedHonor
chosen
Indicates that one entity has formally bestowed an honor, award, or distinction upon another entity.
-
C.
honoredThrough
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
D.
isGivenInHonorOf
Indicates that something (such as an award, gift, or event) is presented or dedicated as a mark of respect or recognition for a particular person or entity.
-
E.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:06 p.m.