Triple
T5872728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beguine community |
E130555
|
entity |
| Predicate | vowStatus |
P67333
|
FINISHED |
| Object | no permanent vows |
—
|
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: no permanent vows | Statement: [Beguine community, vowStatus, no permanent vows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowStatus Context triple: [Beguine community, vowStatus, no permanent vows]
-
A.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
B.
isVowel
Indicates that the referenced character or symbol is a vowel in the relevant alphabet or phonetic system.
-
C.
hasVowelSystem
Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
-
D.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
E.
hasVowelFeature
Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0432f06fc8190bc047d52ffc30d59 |
completed | March 22, 2026, 7:29 p.m. |
Created at: March 22, 2026, 3:56 p.m.