Triple
T31134638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roma |
E793606
|
entity |
| Predicate | hostsEnclave |
P172857
|
FINISHED |
| Object | Vatican City |
—
|
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: Vatican City | Statement: [Roma, hostsEnclave, Vatican City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsEnclave Context triple: [Roma, hostsEnclave, Vatican City]
-
A.
hostArena
Indicates that one entity serves as the arena or venue where an event or activity involving the other entity takes place.
-
B.
hostPark
Indicates that an entity provides space or facilities for a park to be located or held within its area.
-
C.
hostEmpire
Indicates that one entity serves as the imperial authority or ruling empire that hosts, controls, or encompasses another entity.
-
D.
hostLatticeFor
Indicates that one entity serves as the structural lattice framework within which another entity is incorporated, embedded, or accommodated.
-
E.
hostCluster
Indicates a relationship where one cluster serves as the hosting or parent environment for another resource, service, or sub-cluster.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 29, 2026, 9:05 p.m.