Triple
T3072834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rioplatense Spanish |
E64063
|
entity |
| Predicate | replacesForm |
P29646
|
FINISHED |
| Object | tú with vos in everyday speech |
—
|
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: tú with vos in everyday speech | Statement: [Rioplatense Spanish, replacesForm, tú with vos in everyday speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesForm Context triple: [Rioplatense Spanish, replacesForm, tú with vos in everyday speech]
-
A.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another entity.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
subsequentForm
Indicates that one form, version, or state of something occurs later in sequence or development than another.
-
D.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
E.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14e372c81908c25c7f3e7e0c864 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.