Triple
T24335813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayr Rugby Football Club |
E613376
|
entity |
| Predicate | hasRepresentativeFranchise |
P115584
|
FINISHED |
| Object | Ayrshire Bulls |
—
|
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: Ayrshire Bulls | Statement: [Ayr Rugby Football Club, hasRepresentativeFranchise, Ayrshire Bulls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentativeFranchise Context triple: [Ayr Rugby Football Club, hasRepresentativeFranchise, Ayrshire Bulls]
-
A.
hasFranchiseRepresentation
chosen
Indicates that one entity serves as an official franchise representative or outlet for another entity.
-
B.
representsFranchiseOrigin
Indicates that one entity is the original source or originating work from which the other entity’s franchise is derived.
-
C.
hasParentFranchise
Indicates that one franchise entity is the parent or overarching franchise of another franchise entity.
-
D.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
E.
associatedFranchise
Indicates a relationship where one entity is linked to, or belongs within, a particular franchise or franchise universe.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f5346881909ca93b7ceef543ed |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:56 a.m.