Triple
T29528980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaza–Gorani |
E749146
|
entity |
| Predicate | isProposedBy |
P69084
|
FINISHED |
| Object | some linguists |
—
|
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: some linguists | Statement: [Zaza–Gorani, isProposedBy, some linguists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProposedBy Context triple: [Zaza–Gorani, isProposedBy, some linguists]
-
A.
wereProposedBy
chosen
Indicates that one or more entities (such as ideas, plans, or items) were put forward or suggested by a specific agent or source.
-
B.
coProposedBy
Indicates that a proposal, idea, or item is jointly put forward or suggested by multiple entities together.
-
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.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
-
E.
proposedByBody
Indicates that something (such as a decision, measure, or action) has been formally put forward or initiated by a specific governing or organizational body.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 4:50 p.m.