Triple
T30577217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motherwell F.C. women |
E778281
|
entity |
| Predicate | sharesClubIdentityWith |
P68500
|
FINISHED |
| Object | Motherwell F.C. |
—
|
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: Motherwell F.C. | Statement: [Motherwell F.C. women, sharesClubIdentityWith, Motherwell F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesClubIdentityWith Context triple: [Motherwell F.C. women, sharesClubIdentityWith, Motherwell F.C.]
-
A.
sharesIdentityWith
chosen
Indicates that two entities are considered to have the same identity, referring to the very same underlying individual or object rather than merely being similar or related.
-
B.
sharesRecordWith
Indicates that two entities have at least one record or data entry in common, or are both associated with the same record.
-
C.
sharesRegistrationWith
Indicates that two or more entities are associated with the same registration identifier or record.
-
D.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 29, 2026, 8:23 p.m.