Triple
T651257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladino (Judeo-Spanish) |
E11348
|
entity |
| Predicate | preservesFeature |
P17760
|
FINISHED |
| Object | archaic Iberian vocabulary |
—
|
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: archaic Iberian vocabulary | Statement: [Ladino (Judeo-Spanish), preservesFeature, archaic Iberian vocabulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservesFeature Context triple: [Ladino (Judeo-Spanish), preservesFeature, archaic Iberian vocabulary]
-
A.
preservationFactor
Indicates the degree to which something is protected, maintained, or kept intact over time, often moderating how much change, loss, or degradation occurs.
-
B.
aimsToPreserve
Indicates an intention or effort by one entity to maintain, protect, or keep another entity in its current or desired state.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
E.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f33b6d881908b6662b73d6fe833 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.