Triple
T6442577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porta San Giovanni in the Aurelian Walls |
E138259
|
entity |
| Predicate | hasSingleArch |
P3282
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Porta San Giovanni in the Aurelian Walls, hasSingleArch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleArch Context triple: [Porta San Giovanni in the Aurelian Walls, hasSingleArch, true]
-
A.
hasSingle
chosen
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
B.
hasSubArchitecture
Indicates that one architectural component or structure is a subordinate or constituent part of a larger overarching architecture.
-
C.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
-
D.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
E.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06989dfb88190b25ff8b2c53f3ced |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.