Triple
T24631281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Pantheon, Lisbon |
E609681
|
entity |
| Predicate | roofAccess |
P58825
|
FINISHED |
| Object | panoramic terrace |
—
|
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: panoramic terrace | Statement: [National Pantheon, Lisbon, roofAccess, panoramic terrace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofAccess Context triple: [National Pantheon, Lisbon, roofAccess, panoramic terrace]
-
A.
hasDomeOrRoofAccess
chosen
Indicates that an entity has access to, or the ability to reach or use, a dome or roof area associated with another entity.
-
B.
floorAccess
Indicates that an entity is permitted to enter or use a specific floor or level within a building or structure.
-
C.
roofCanBe
Indicates that something is capable of serving as or functioning as a roof for something else.
-
D.
roofStatus
Indicates the current condition or state of a roof, such as whether it is intact, damaged, under repair, or replaced.
-
E.
roofLevel
Indicates the vertical level or story of a building at which the roof is located or begins.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.