Triple
T38307850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Meadow Creek |
E1033600
|
entity |
| Predicate | discoveryOccurredAt |
P3985
|
FINISHED |
| Object | Reed farm |
—
|
NE NERFINISHED |
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: Reed farm | Statement: [Little Meadow Creek, discoveryOccurredAt, Reed farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOccurredAt Context triple: [Little Meadow Creek, discoveryOccurredAt, Reed farm]
-
A.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
B.
remainsDiscoveredOn
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
-
C.
hasDiscoveryAnnouncementDate
Indicates the date on which the discovery of an entity was formally announced or made public.
-
D.
wasDiscoveredAt
chosen
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
discoveryDate
Indicates the date on which something was first discovered or identified.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:30 p.m.