Triple
T2253951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mestizo |
E49676
|
entity |
| Predicate | termVariesBy |
P36743
|
FINISHED |
| Object | country |
—
|
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: country | Statement: [Mestizo, termVariesBy, country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termVariesBy Context triple: [Mestizo, termVariesBy, country]
-
A.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
B.
viewVariesAmong
Indicates that the way something is viewed, perceived, or interpreted differs across multiple entities or contexts.
-
C.
locationVariesWith
Indicates that the location of one entity changes in dependence on, or as a function of, changes in another entity.
-
D.
lengthVariesBy
Indicates that the length of one entity changes or differs depending on another specified factor or condition.
-
E.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc12029548190af9f2cdd7a4de2d6 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:47 p.m.