Triple
T27159976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fowles |
E682632
|
entity |
| Predicate | canBeMarriedName |
P46960
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fowles, canBeMarriedName, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMarriedName Context triple: [Fowles, canBeMarriedName, yes]
-
A.
canBeMiddleName
Indicates that one entity is suitable or allowed to serve as the middle name of another entity.
-
B.
canBeLegalGivenName
Indicates that a given name satisfies the rules or conditions required to be considered legally valid.
-
C.
mayBeMarried
Indicates that two entities have a possible marital relationship, but it is not confirmed as definite.
-
D.
canBeFamilyName
chosen
Indicates that something is capable of functioning as a family name or surname in at least one context.
-
E.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 9:18 a.m.