Triple
T10750580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parji |
E253560
|
entity |
| Predicate | hasNounPostpositions |
P15729
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parji, hasNounPostpositions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNounPostpositions Context triple: [Parji, hasNounPostpositions, yes]
-
A.
usesPostpositions
chosen
Indicates that one entity employs postpositions, placing relational or grammatical markers after the words they modify rather than before them.
-
B.
hasPrepositions
Indicates that one entity includes, uses, or is associated with one or more prepositions in relation to another entity.
-
C.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
D.
hasPreposition
Indicates that one entity is associated with or linked to another entity through a specific prepositional relationship.
-
E.
hasNounClassSystem
Indicates that an entity possesses a grammatical system in which nouns are categorized into distinct classes that affect their agreement with other elements in the language.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dbfe5f481908eed42328447b158 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.