Triple
T29963945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My People |
E761120
|
entity |
| Predicate | hasOriginalLanguageVersion |
P5477
|
FINISHED |
| Object | Mi Gente |
—
|
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: Mi Gente | Statement: [My People, hasOriginalLanguageVersion, Mi Gente]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalLanguageVersion Context triple: [My People, hasOriginalLanguageVersion, Mi Gente]
-
A.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
B.
originalPublicationLanguageVariant
chosen
Indicates that one language is a specific variant or version of the language in which a work was originally published.
-
C.
hasOriginalCountryTitle
Indicates that an entity is associated with the title it originally had in its country of origin.
-
D.
originalLanguageStatus
Indicates the status or condition of something with respect to its original language (e.g., whether it is in, derived from, or altered from the language in which it was first created).
-
E.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 6:29 p.m.