Triple
T5829587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bzyb dialect |
E129310
|
entity |
| Predicate | hasAgreementSystem |
P67423
|
FINISHED |
| Object | extensive person and number agreement on the verb |
—
|
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: extensive person and number agreement on the verb | Statement: [Bzyb dialect, hasAgreementSystem, extensive person and number agreement on the verb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgreementSystem Context triple: [Bzyb dialect, hasAgreementSystem, extensive person and number agreement on the verb]
-
A.
hasTypeOfAgreement
Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
-
B.
canEnterIntoAgreementsWith
Indicates that one entity has the legal or formal capacity to make binding agreements or contracts with another entity.
-
C.
hasAccord
Indicates that there is a formal agreement, harmony, or concord between the related entities.
-
D.
establishedByAgreementSignedIn
Indicates that something was formally created or instituted as a result of an agreement that was signed at a specific time or place.
-
E.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
- F. None of above. chosen
Provenance (4 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:54 p.m.