Triple
T17202141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munda–Nicobarese branch |
E417500
|
entity |
| Predicate | proposedWithin |
P13994
|
FINISHED |
| Object | historical-comparative linguistics |
—
|
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: historical-comparative linguistics | Statement: [Munda–Nicobarese branch, proposedWithin, historical-comparative linguistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedWithin Context triple: [Munda–Nicobarese branch, proposedWithin, historical-comparative linguistics]
-
A.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
B.
proposedInContextOf
chosen
Indicates that something (such as an idea, action, or change) was proposed specifically within, and in relation to, a particular situation, setting, or surrounding circumstances.
-
C.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
D.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
E.
proposedPart
Indicates that one entity has been suggested or put forward to serve as a component or element 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db014b08190b88a5001e9f7811b |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.