Triple
T13467472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marathi–Konkani languages |
E311539
|
entity |
| Predicate | shareFeatureWith |
P7447
|
FINISHED |
| Object | Marathi-Konkani dialect continuum |
—
|
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: Marathi-Konkani dialect continuum | Statement: [Marathi–Konkani languages, shareFeatureWith, Marathi-Konkani dialect continuum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareFeatureWith Context triple: [Marathi–Konkani languages, shareFeatureWith, Marathi-Konkani dialect continuum]
-
A.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
B.
shareFeature
chosen
Indicates that two or more entities possess at least one common attribute, property, or characteristic.
-
C.
sharesRouteWith
Indicates that two entities follow or operate along the same or overlapping route.
-
D.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
E.
sharesAuthorWith
Indicates that two entities have at least one author in common.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf101a1081909f2aba6da47baacc |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.