Triple
T10489605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabu |
E247379
|
entity |
| Predicate | hasGrammaticalDescription |
P59173
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Sabu, hasGrammaticalDescription, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrammaticalDescription Context triple: [Sabu, hasGrammaticalDescription, partial]
-
A.
grammaticalDescription
chosen
Indicates that one entity provides a description or explanation of the grammatical properties or structure of another entity.
-
B.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
C.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
D.
grammaticalType
Indicates the grammatical category or role (such as part of speech or syntactic function) that an expression has within a language.
-
E.
grammaticalStructure
Indicates the way linguistic elements are organized and related within a sentence or phrase according to grammatical rules.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.