Triple
T25068490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonalli |
E627845
|
entity |
| Predicate | canBeStrengthenedBy |
P13002
|
FINISHED |
| Object | offerings |
—
|
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: offerings | Statement: [Tonalli, canBeStrengthenedBy, offerings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStrengthenedBy Context triple: [Tonalli, canBeStrengthenedBy, offerings]
-
A.
strengthensFrom
chosen
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
B.
strengthenedPowerIn
Indicates that one entity has increased, reinforced, or consolidated its power, influence, or control within a particular context, domain, or location represented by the other entity.
-
C.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
D.
canBePoweredUp
Indicates that an entity has the capability to receive additional power or energy, enhancing its state or functionality.
-
E.
strengthenedStatusOf
Indicates that the status, condition, or standing of one entity has been made stronger or more robust in relation to another entity or context.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:10 a.m.