Triple
T4761156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samson |
E105700
|
entity |
| Predicate | vowType |
P23834
|
FINISHED |
| Object | Nazirite vow |
—
|
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: Nazirite vow | Statement: [Samson, vowType, Nazirite vow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowType Context triple: [Samson, vowType, Nazirite vow]
-
A.
hasVow
chosen
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
B.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
C.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
D.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
E.
hasVowelSystem
Indicates that an entity possesses a particular system or pattern of vowel sounds (a structured set of vowel phonemes or contrasts).
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.