Triple
T36826493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | São Brás |
E910023
|
entity |
| Predicate | isInvokedFor |
P173448
|
FINISHED |
| Object | healing of throat diseases |
—
|
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: healing of throat diseases | Statement: [São Brás, isInvokedFor, healing of throat diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInvokedFor Context triple: [São Brás, isInvokedFor, healing of throat diseases]
-
A.
isUsedToInvoke
chosen
Indicates that one entity serves as a means or mechanism to trigger, call, or activate another entity or process.
-
B.
containsInvocation
Indicates that one entity includes or embeds a call to another operation, function, or method within it.
-
C.
isExecutedFor
Indicates that an action, plan, or process is carried out on behalf of, or in service of, a particular entity or purpose.
-
D.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
E.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9c9ef88190b71bcc6f5b4a6182 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.