Triple
T17027476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jovan |
E413103
|
entity |
| Predicate | hasDiminutive |
P456
|
FINISHED |
| Object | Joca |
E1075065
|
NE 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: Joca | Statement: [Jovan, hasDiminutive, Joca]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joca Context triple: [Jovan, hasDiminutive, Joca]
-
A.
Joca
chosen
Joca is a Portuguese diminutive form of the male given name João, commonly used as an affectionate nickname.
-
B.
Jiloca
Jiloca is a river in northeastern Spain that flows through the autonomous community of Aragon, contributing to the region’s agricultural and natural landscapes.
-
C.
Juncalinho
Juncalinho is a small coastal settlement on the island of São Nicolau in Cape Verde, known for its fishing community and scenic Atlantic shoreline.
-
D.
Jino
Jino are an officially recognized ethnic minority group in China, primarily living in Yunnan Province and known for their distinct language and traditional culture.
-
E.
Jao
Jao is a variant transliteration of the Chinese surname commonly rendered as Zhao.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d728148190b83367cd6fdefa50 |
completed | April 18, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a011b53306081908972a0a5db474b6c |
completed | May 10, 2026, 11:57 p.m. |
Created at: April 10, 2026, 5:33 a.m.