Triple
T7988410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Backyard Bird Count |
E185740
|
entity |
| Predicate | observationUnit |
P10521
|
FINISHED |
| Object | individual birds counted |
—
|
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: individual birds counted | Statement: [Great Backyard Bird Count, observationUnit, individual birds counted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationUnit Context triple: [Great Backyard Bird Count, observationUnit, individual birds counted]
-
A.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
B.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
C.
samplingUnit
chosen
Indicates that one entity serves as the basic unit or element from which samples are drawn or measured in a sampling process.
-
D.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
E.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4e47308190918b67fb6eac9046 |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.