Triple
T137613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrés |
E2780
|
entity |
| Predicate | usedInCommunity |
P5924
|
FINISHED |
| Object | Spanish-speaking communities worldwide |
—
|
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: Spanish-speaking communities worldwide | Statement: [Andrés, usedInCommunity, Spanish-speaking communities worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCommunity Context triple: [Andrés, usedInCommunity, Spanish-speaking communities worldwide]
-
A.
usedInCity
Indicates that something is utilized, applied, or operates within the context or boundaries of a particular city.
-
B.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
E.
hasOnlineCommunity
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a6cab88190944c8f74d8d1605c |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.