Triple
T25068436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mictlan |
E627844
|
entity |
| Predicate | requiresAidFrom |
P43085
|
FINISHED |
| Object | dog to cross a river |
—
|
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: dog to cross a river | Statement: [Mictlan, requiresAidFrom, dog to cross a river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAidFrom Context triple: [Mictlan, requiresAidFrom, dog to cross a river]
-
A.
requiresAssistanceFrom
chosen
Indicates that one entity depends on help, support, or intervention from another entity to perform an action or fulfill a need.
-
B.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
C.
conditionForAid
Indicates that one entity constitutes a requirement or qualifying circumstance that must be met for another entity to receive aid or assistance.
-
D.
requiresCaredForPersonToReceive
Indicates that one entity’s receipt of something is conditional on a specific cared-for person also receiving it.
-
E.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 6:10 a.m.