Triple
T8458590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakaar |
E199981
|
entity |
| Predicate | receivesDebrisFrom |
P4382
|
FINISHED |
| Object | wormholes |
—
|
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: wormholes | Statement: [Sakaar, receivesDebrisFrom, wormholes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesDebrisFrom Context triple: [Sakaar, receivesDebrisFrom, wormholes]
-
A.
debrisRecoveryEffort
Indicates efforts or actions undertaken to locate, collect, and secure debris resulting from an incident or event.
-
B.
receivesCargoFrom
Indicates that one entity obtains or is delivered cargo from another entity.
-
C.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
D.
debrisFieldStates
Indicates the various conditions or statuses associated with a particular debris field over time or in a given context.
-
E.
hasTrashReceptacles
Indicates that one entity provides, contains, or is equipped with trash receptacles for waste disposal in relation to another entity or location.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49e036c8190abb50ca272266ca6 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.