Triple
T37459139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crackle |
E930873
|
entity |
| Predicate | collectibleInRegion |
P77092
|
FINISHED |
| Object | NA |
—
|
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: NA | Statement: [Crackle, collectibleInRegion, NA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectibleInRegion Context triple: [Crackle, collectibleInRegion, NA]
-
A.
collectibleIn
chosen
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
B.
collectibleFor
Indicates that one entity is intended or suitable to be collected by, or kept as part of a collection for, another entity.
-
C.
collectingArea
Indicates the total surface area over which something (typically a device or system) gathers or receives a substance, signal, or resource.
-
D.
collectionIncludesRegion
Indicates that a collection contains or encompasses a specified region as one of its constituent parts.
-
E.
collectibleAspect
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:17 p.m.