Triple
T9047315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Chernomorets Novorossiysk |
E216786
|
entity |
| Predicate | hasHomeSupport |
P86067
|
FINISHED |
| Object | local fans in Novorossiysk |
—
|
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: local fans in Novorossiysk | Statement: [FC Chernomorets Novorossiysk, hasHomeSupport, local fans in Novorossiysk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeSupport Context triple: [FC Chernomorets Novorossiysk, hasHomeSupport, local fans in Novorossiysk]
-
A.
hasHomeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
B.
hasHouseholdFeature
Indicates that a household possesses or includes a specific feature, attribute, or amenity.
-
C.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
D.
hasAgencySupport
Indicates that an entity receives backing, assistance, or sponsorship from an agency.
-
E.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b5022c88190ab6b6de3c3830a41 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:09 p.m.