Triple
T32529374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Miranda |
E831403
|
entity |
| Predicate | correPor |
P180664
|
FINISHED |
| Object | município de Miranda |
—
|
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: município de Miranda | Statement: [Rio Miranda, correPor, município de Miranda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correPor Context triple: [Rio Miranda, correPor, município de Miranda]
-
A.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
-
B.
endedFor
Indicates that a particular event, state, or process has come to an end for a specified entity or participant.
-
C.
correspondedWith
Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
-
D.
carryOut
Indicates performing or executing an action, task, or plan to completion.
-
E.
portée
Indicates that one entity carries, bears, or supports another entity physically or figuratively.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: May 1, 2026, 1:01 a.m.