Triple
T26806531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axelina |
E671851
|
entity |
| Predicate | namePositionInFullName |
P1082
|
FINISHED |
| Object | middle name |
—
|
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: middle name | Statement: [Axelina, namePositionInFullName, middle name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namePositionInFullName Context triple: [Axelina, namePositionInFullName, middle name]
-
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.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
C.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
D.
nameElementIn
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
E.
givenNamePortion
Indicates that one string represents a portion or segment of a person's given (first) name.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a1e50ac8190802584e63794ab81 |
completed | May 2, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:26 a.m.