Triple
T10334184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synthia |
E242955
|
entity |
| Predicate | hasTypicalPositionInFullName |
P1082
|
FINISHED |
| Object | given name position |
—
|
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: given name position | Statement: [Synthia, hasTypicalPositionInFullName, given name position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPositionInFullName Context triple: [Synthia, hasTypicalPositionInFullName, given name position]
-
A.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
B.
usedInFullNameOf
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
C.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
D.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
-
E.
fullNameIncludes
Indicates that one entity’s full name contains another specified string or name component as a substring.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:53 a.m.