Triple
T25178515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Coast Suns (AFLW) |
E630517
|
entity |
| Predicate | sharesLogoWith |
P48444
|
FINISHED |
| Object | Gold Coast Suns |
—
|
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: Gold Coast Suns | Statement: [Gold Coast Suns (AFLW), sharesLogoWith, Gold Coast Suns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLogoWith Context triple: [Gold Coast Suns (AFLW), sharesLogoWith, Gold Coast Suns]
-
A.
sharesNameWith
Indicates that two entities have the same name or an identical naming designation.
-
B.
sharesBrandingWith
chosen
Indicates that two entities use the same or closely related branding elements, such as name, logo, or visual identity.
-
C.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
D.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 21, 2026, 12:35 p.m.