Triple
T22273728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberavon RFC |
E550546
|
entity |
| Predicate | hasStrongCommunitySupport |
P146586
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aberavon RFC, hasStrongCommunitySupport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongCommunitySupport Context triple: [Aberavon RFC, hasStrongCommunitySupport, true]
-
A.
hasStrongCommunity
chosen
Indicates that an entity is associated with a highly engaged, supportive, and cohesive community.
-
B.
hasCommunitySupport
Indicates that an entity is backed, endorsed, or positively received by a community or group of users.
-
C.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
D.
supportsCommunityContent
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
E.
hasOnlineCommunity
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
- 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea547e4819098baf88f3c605242 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.