Triple
T26032658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raccoon Mario |
E647474
|
entity |
| Predicate | canHover |
P159887
|
FINISHED |
| Object | By rapidly wagging tail |
—
|
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: By rapidly wagging tail | Statement: [Raccoon Mario, canHover, By rapidly wagging tail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHover Context triple: [Raccoon Mario, canHover, By rapidly wagging tail]
-
A.
canTarget
Indicates that one entity is able or permitted to select, aim at, or direct its action or effect toward another entity as a target.
-
B.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
C.
canIndicate
Indicates that one entity has the potential or capacity to serve as a sign, signal, or evidence of another entity or condition.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061b1b5081908dc5e2ac3ac58619 |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 9:06 a.m.