Triple
T18368682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multnomah dialect |
E440119
|
entity |
| Predicate | peopleAlsoSpeak |
P741
|
FINISHED |
| Object | English (in modern times) |
—
|
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: English (in modern times) | Statement: [Multnomah dialect, peopleAlsoSpeak, English (in modern times)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peopleAlsoSpeak Context triple: [Multnomah dialect, peopleAlsoSpeak, English (in modern times)]
-
A.
peopleAlsoCall
Indicates that an entity is alternatively referred to by another name, label, or alias used by people.
-
B.
speaksWith
Indicates that one entity engages in spoken communication or conversation with another entity.
-
C.
speaksIn
Indicates that an entity uses or expresses itself in a particular language or medium when speaking.
-
D.
languagesSpoken
chosen
Indicates that an entity is able to communicate using one or more specified languages.
-
E.
isSpokenAround
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e51750d3dc8190b153046c1171ee2b |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:38 a.m.