Triple
T13574704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakitia |
E324250
|
entity |
| Predicate | notableDifferenceFrom |
P88519
|
FINISHED |
| Object | Ladino |
—
|
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: Ladino | Statement: [Hakitia, notableDifferenceFrom, Ladino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDifferenceFrom Context triple: [Hakitia, notableDifferenceFrom, Ladino]
-
A.
notableComparison
Indicates that one entity is being compared to another in a way that is especially significant, remarkable, or worthy of note.
-
B.
notableVariation
chosen
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within a given context.
-
C.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
D.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
E.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.