Triple
T21101044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wei |
E519903
|
entity |
| Predicate | surnamePosition |
P1082
|
FINISHED |
| Object | beforeGivenName |
—
|
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: beforeGivenName | Statement: [Wei, surnamePosition, beforeGivenName]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnamePosition Context triple: [Wei, surnamePosition, beforeGivenName]
-
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.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
C.
positionOfNamesake
Indicates that one entity occupies the role, rank, or spatial/organizational position associated with another entity for which it is named.
-
D.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
-
E.
firstSurnameListed
Indicates that the referenced surname is the first one appearing in an ordered list of surnames associated with an entity.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5e16cc81908257ccf8c9a59117 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.