Triple
T35482134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alayne Stone |
E1025495
|
entity |
| Predicate | bastardSurnameRegion |
P119132
|
FINISHED |
| Object | the Vale |
—
|
NE NERFINISHED |
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: the Vale | Statement: [Alayne Stone, bastardSurnameRegion, the Vale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bastardSurnameRegion Context triple: [Alayne Stone, bastardSurnameRegion, the Vale]
-
A.
bastardSurname
Indicates that a person uses a surname traditionally associated with illegitimate birth or non-marital parentage.
-
B.
surnameLikelyOriginRegion
Indicates the geographic region from which a person’s surname is most likely to have originated.
-
C.
hasSurnameRegionAssociation
chosen
Indicates that there is a relationship between a surname and a geographic region, such as origin, prevalence, or cultural association.
-
D.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
-
E.
EuropeanNameVariant
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.