Triple
T30077990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wm. Power |
E764375
|
entity |
| Predicate | expandsToFamilyName |
P46960
|
FINISHED |
| Object | Power |
—
|
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: Power | Statement: [Wm. Power, expandsToFamilyName, Power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsToFamilyName Context triple: [Wm. Power, expandsToFamilyName, Power]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
canBeFamilyName
chosen
Indicates that something is capable of functioning as a family name or surname in at least one context.
-
C.
hasFamilyNameAfterConversion
Indicates that an entity has a specific family name adopted or used after a religious, cultural, or legal conversion event.
-
D.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
E.
isOriginalFamilyNameOf
Indicates that a given family name is the original or birth surname of a person, from which any later or changed surnames may have derived.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:02 p.m.