Triple
T25761545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassidy |
E648751
|
entity |
| Predicate | isAdaptedFrom |
P94989
|
FINISHED |
| Object | Irish family name |
—
|
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: Irish family name | Statement: [Cassidy, isAdaptedFrom, Irish family name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdaptedFrom Context triple: [Cassidy, isAdaptedFrom, Irish family name]
-
A.
adaptsFrom
Indicates that one entity is derived, modified, or transformed from another, preserving core elements while changing form, medium, or context.
-
B.
hasWorkAdaptedFrom
chosen
Indicates that one work is derived, adapted, or transformed from another pre-existing work.
-
C.
hasBeenAdaptedBy
Indicates that an original work has been transformed or re-created into a new form or medium by a particular adapter.
-
D.
adoptedFrom
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
E.
adaptedWithin
Indicates that one entity has been modified, adjusted, or tailored to function appropriately within the context, scope, or boundaries defined by another entity.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf06c588190bd5438a52bf1742c |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:06 a.m.