Triple
T34215357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monumento de Interesse Público |
E877769
|
entity |
| Predicate | hasRelatedStatus |
P45754
|
FINISHED |
| Object | Monumento Nacional |
—
|
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: Monumento Nacional | Statement: [Monumento de Interesse Público, hasRelatedStatus, Monumento Nacional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedStatus Context triple: [Monumento de Interesse Público, hasRelatedStatus, Monumento Nacional]
-
A.
hasSiblingStatus
Indicates that there exists a sibling relationship between two entities, specifying their status as siblings to each other.
-
B.
associatedStatus
chosen
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
hasRelationships
Indicates that an entity is connected to one or more other entities through specified types of relationships.
-
E.
hasRelatedResult
Indicates that one entity has an associated outcome, effect, or result that is meaningfully connected to it.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.