Triple
T38513989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yazoo people |
E921989
|
entity |
| Predicate | presentInHistoricalSourceLanguage |
P150962
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Yazoo people, presentInHistoricalSourceLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInHistoricalSourceLanguage Context triple: [Yazoo people, presentInHistoricalSourceLanguage, French]
-
A.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
B.
hasLanguageEvidenceOf
Indicates that there is linguistic or textual evidence supporting, documenting, or attesting to the related entity or claim.
-
C.
namedInHistoricalSources
chosen
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
-
D.
presentedInLanguage
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
-
E.
hasHistoricalText
Indicates that an entity is associated with a historical written document or record describing it or its past.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.