Triple
T12842628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GA-bri-e-le |
E307089
|
entity |
| Predicate | emphasisPosition |
P17414
|
FINISHED |
| Object | initial syllable |
—
|
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: initial syllable | Statement: [GA-bri-e-le, emphasisPosition, initial syllable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasisPosition Context triple: [GA-bri-e-le, emphasisPosition, initial syllable]
-
A.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
B.
focusPosition
Indicates the spatial or logical position at which attention, concentration, or processing is currently directed within a given context.
-
C.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
D.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
E.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:35 p.m.