Triple
T34515379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liam Moone |
E886136
|
entity |
| Predicate | hasFamilyNameCharacter |
P190062
|
FINISHED |
| Object | Debra Moone |
—
|
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: Debra Moone | Statement: [Liam Moone, hasFamilyNameCharacter, Debra Moone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyNameCharacter Context triple: [Liam Moone, hasFamilyNameCharacter, Debra Moone]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
hasFamilyNameElement
Indicates that an entity has a specific component or segment that forms part of its family name.
-
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.
hasFamilyNameInitial
chosen
Indicates that an entity’s family name begins with a specified initial letter or character.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 2:01 a.m.