Triple
T32506174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapa, Rio de Janeiro |
E830801
|
entity |
| Predicate | currentFunctionOfMainLandmark |
P5507
|
FINISHED |
| Object | tram viaduct |
—
|
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: tram viaduct | Statement: [Lapa, Rio de Janeiro, currentFunctionOfMainLandmark, tram viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentFunctionOfMainLandmark Context triple: [Lapa, Rio de Janeiro, currentFunctionOfMainLandmark, tram viaduct]
-
A.
mainBuildingCurrentFunction
Indicates the current primary use or role that the main building serves.
-
B.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
C.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular city.
-
D.
hasMonumentFunction
Indicates that something serves the role or purpose of a monument, such as commemorating, honoring, or symbolizing a person, event, or idea.
-
E.
currentFunction
chosen
Indicates that an entity is presently serving in a specific role, position, or capacity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1 a.m.