Triple
T29862504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inis |
E758357
|
entity |
| Predicate | conjugationType |
P167679
|
FINISHED |
| Object | irregular 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: irregular verb | Statement: [Inis, conjugationType, irregular verb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conjugationType Context triple: [Inis, conjugationType, irregular verb]
-
A.
isConjugatedTo
Indicates that two verb forms are related as different inflectional variants of the same verb through conjugation.
-
B.
conjugate
Indicates that one entity is a grammatical or mathematical counterpart of another, linked by a specific transformation such as verb inflection or complex-number pairing.
-
C.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
D.
isCombinedFormOf
Indicates that one entity is a composite or merged form that results from combining two or more other entities.
-
E.
grammaticalMood
Indicates the grammatical mood used in an utterance, specifying the speaker’s attitude toward the action or state (such as indicative, imperative, or subjunctive).
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676868f148190a6e39745c76e36ff |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:50 p.m.