Triple
T34286752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Looj |
E879759
|
entity |
| Predicate | typicalDebris |
P185578
|
FINISHED |
| Object | leaves |
—
|
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: leaves | Statement: [Looj, typicalDebris, leaves]
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 (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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.