Triple
T34286752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Looj |
E879759
|
entity |
| Predicate | typicalDebris |
—
|
GENERATED |
| Object | leaves |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDebris Context triple: [Looj, typicalDebris, leaves]
-
A.
debris
chosen
Indicates that one entity consists of or is characterized by scattered fragments or remains resulting from the destruction, breakage, or deterioration of another entity.
-
B.
debrisRecovered
Indicates that debris resulting from an event or incident has been successfully located, collected, and retrieved.
-
C.
debrisConcern
Indicates a relationship where an entity expresses worry, attention, or consideration regarding debris or unwanted material.
-
D.
debrisRecoveryEffort
Indicates efforts or actions undertaken to locate, collect, and secure debris resulting from an incident or event.
-
E.
debrisFieldStates
Indicates the various conditions or statuses associated with a particular debris field over time or in a given context.
- F. None of above.
Provenance (1 batch)
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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.