Triple
T28019200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | common loon |
E707638
|
entity |
| Predicate | territorialCall |
P166861
|
FINISHED |
| Object | yodel |
—
|
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: yodel | Statement: [common loon, territorialCall, yodel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialCall Context triple: [common loon, territorialCall, yodel]
-
A.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
-
B.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
C.
regionNumber
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
-
D.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
E.
territoryCode
Indicates the standardized code assigned to a specific geographic or administrative territory in the relationship.
- F. None of above. chosen
Provenance (4 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_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 27, 2026, 8:09 p.m.