Triple
T5387094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Romance |
E120226
|
entity |
| Predicate | hasSyntacticTrait |
P7162
|
FINISHED |
| Object | increased use of prepositions |
—
|
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: increased use of prepositions | Statement: [Western Romance, hasSyntacticTrait, increased use of prepositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyntacticTrait Context triple: [Western Romance, hasSyntacticTrait, increased use of prepositions]
-
A.
syntacticType
Indicates the grammatical or structural category that characterizes how an expression functions within a syntactic construction.
-
B.
hasLinguisticFeature
chosen
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
C.
hasSyllabicStructure
Indicates that an entity possesses a specific arrangement or pattern of syllables, such as their number, order, or type.
-
D.
hasSyllableStructure
Indicates that an entity (typically a word or morpheme) possesses a particular arrangement or pattern of syllables.
-
E.
hasVerbalFeature
Indicates that an entity possesses a specific verbal property, characteristic, or behavior related to speech or 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f8d81081909174027a4fe640f2 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.