Triple
T28016628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon thundereggs |
E707559
|
entity |
| Predicate | collectingActivity |
P131392
|
FINISHED |
| Object | rockhounding |
—
|
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: rockhounding | Statement: [Oregon thundereggs, collectingActivity, rockhounding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectingActivity Context triple: [Oregon thundereggs, collectingActivity, rockhounding]
-
A.
collectingArea
Indicates the total surface area over which something (typically a device or system) gathers or receives a substance, signal, or resource.
-
B.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
-
C.
collectingFocus
chosen
Indicates that an entity is directing attention or effort toward gathering or assembling items, information, or resources.
-
D.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
E.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 8:07 p.m.