Triple
T1048942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runasimi |
E22648
|
entity |
| Predicate | borrowedFrom |
P18996
|
FINISHED |
| Object | Spanish language |
—
|
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 language | Statement: [Runasimi, borrowedFrom, Spanish language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borrowedFrom Context triple: [Runasimi, borrowedFrom, Spanish language]
-
A.
hasBorrowingsFrom
chosen
Indicates that one entity has taken, adopted, or derived elements (such as features, ideas, or content) from another entity.
-
B.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
C.
library
Indicates that an entity functions as or is associated with a library, typically as a place or system for storing, organizing, and providing access to collections of information resources.
-
D.
purchasedFrom
Indicates that one entity bought or acquired something from another entity as the seller or source.
-
E.
leasedFrom
Indicates that one entity is renting or leasing something from another entity, which acts as the owner or lessor.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.