Triple
T25605653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kack |
E641902
|
entity |
| Predicate | hasFamilyNamePattern |
P65792
|
FINISHED |
| Object | rhyming -ack names |
—
|
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: rhyming -ack names | Statement: [Kack, hasFamilyNamePattern, rhyming -ack names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyNamePattern Context triple: [Kack, hasFamilyNamePattern, rhyming -ack names]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
hasSurnamePattern
chosen
Indicates that an entity’s surname follows or matches a specified structural or stylistic pattern.
-
C.
hasFamilyNameElement
Indicates that an entity has a specific component or segment that forms part of its family name.
-
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.
hasFamilyNameAfterConversion
Indicates that an entity has a specific family name adopted or used after a religious, cultural, or legal conversion event.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 4:38 p.m.