Triple
T36537224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhsin |
E900619
|
entity |
| Predicate | isDerivedFromVerb |
P909
|
FINISHED |
| Object | ahsana (to do good, to act benevolently) |
—
|
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: ahsana (to do good, to act benevolently) | Statement: [Muhsin, isDerivedFromVerb, ahsana (to do good, to act benevolently)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerivedFromVerb Context triple: [Muhsin, isDerivedFromVerb, ahsana (to do good, to act benevolently)]
-
A.
isDerivedFromCommonNoun
Indicates that one term is formed or obtained from a common noun, reflecting a derivational relationship between the two.
-
B.
hasVerbClass
Indicates that an action or event is categorized into a specific verb class based on its grammatical or semantic behavior.
-
C.
hasVerbSystemFrom
Indicates that one language or linguistic system derives or adopts its verb system from another source language or system.
-
D.
isConjugatedTo
Indicates that two verb forms are related as different inflectional variants of the same verb through conjugation.
-
E.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.