Triple
T30478635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monic languages |
E775512
|
entity |
| Predicate | isClosestRelativeOf |
P8563
|
FINISHED |
| Object | Mon language |
—
|
NE NERFINISHED |
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: Mon language | Statement: [Monic languages, isClosestRelativeOf, Mon language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClosestRelativeOf Context triple: [Monic languages, isClosestRelativeOf, Mon language]
-
A.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
B.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
C.
closestLivingRelatives
chosen
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
-
D.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
E.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6871ae044819096fece430cc1f9f9 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:12 p.m.