Triple
T5276138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammospiza maritima |
E119374
|
entity |
| Predicate | vocalizationContext |
P35625
|
FINISHED |
| Object | sings from exposed perches in marshes |
—
|
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: sings from exposed perches in marshes | Statement: [Ammospiza maritima, vocalizationContext, sings from exposed perches in marshes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalizationContext Context triple: [Ammospiza maritima, vocalizationContext, sings from exposed perches in marshes]
-
A.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
B.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
C.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
D.
vocalizationUsage
chosen
Indicates how a particular vocalization is used or applied within a communicative or behavioral context.
-
E.
languageOfVocalization
Indicates the language in which a vocalization (such as speech or singing) is produced.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:51 p.m.