Triple
T26935438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesseract |
E678363
|
entity |
| Predicate | canBeHandledBy |
P93432
|
FINISHED |
| Object | Extremely powerful beings |
—
|
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: Extremely powerful beings | Statement: [Tesseract, canBeHandledBy, Extremely powerful beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHandledBy Context triple: [Tesseract, canBeHandledBy, Extremely powerful beings]
-
A.
canHandle
Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
-
B.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
C.
mayAlsoHandle
Indicates that an entity, in addition to its primary responsibilities, is permitted or capable of handling another specified task, role, or item.
-
D.
canBePassedTo
chosen
Indicates that one entity is capable of being transferred, handed over, or given to another entity.
-
E.
usedToHandle
Indicates that one entity previously managed, processed, or dealt with another entity as part of its function or role.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 6:15 a.m.