Triple
T27741246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stipiturus |
E701859
|
entity |
| Predicate | vernacularNameOfMembers |
P80396
|
FINISHED |
| Object | southern emu-wren |
—
|
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: southern emu-wren | Statement: [Stipiturus, vernacularNameOfMembers, southern emu-wren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vernacularNameOfMembers Context triple: [Stipiturus, vernacularNameOfMembers, southern emu-wren]
-
A.
languageOfMembers
Indicates that the specified language is used or spoken by the members of a given group or organization.
-
B.
vernacularNameAppliedTo
chosen
Indicates that a particular common or vernacular name is assigned or applied to an entity.
-
C.
multilingualName
Indicates that an entity has one or more names expressed in multiple natural languages.
-
D.
vernacularGroup
Indicates a relationship where entities are grouped or associated based on sharing the same vernacular (local or commonly spoken) language.
-
E.
vernacularOf
Indicates that one language or dialect is the everyday, locally used form corresponding to another, more general or standard language.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637169d6c8190bf74d5b882d2eb7d |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:11 p.m.