Triple
T23959494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Monarchs |
E603884
|
entity |
| Predicate | operatedAsAffiliateFrom |
P154045
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Manchester Monarchs, operatedAsAffiliateFrom, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsAffiliateFrom Context triple: [Manchester Monarchs, operatedAsAffiliateFrom, 2001]
-
A.
hasAffiliate
Indicates that one entity is formally associated with another as an affiliate, typically through a partnership, membership, or subordinate organizational relationship.
-
B.
operatedFrom
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
hasAffiliatesIn
Indicates that an entity maintains affiliated entities, branches, or partners located within a specified place or region.
-
E.
bannerAffiliation
Indicates that an entity is associated with, represented by, or operating under a particular banner, label, or identifying heading.
- F. None of above. chosen
Provenance (4 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d91cd481908f53ce7ee569c0f9 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:22 p.m.