Triple
T28393937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laudium |
E719231
|
entity |
| Predicate | hasCommunityInstitutionType |
P39016
|
FINISHED |
| Object | sports club |
—
|
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: sports club | Statement: [Laudium, hasCommunityInstitutionType, sports club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityInstitutionType Context triple: [Laudium, hasCommunityInstitutionType, sports club]
-
A.
hasCommunityInstitutions
chosen
Indicates that an entity possesses, hosts, or is associated with organized community-serving institutions (such as local organizations, centers, or facilities) within its scope.
-
B.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
C.
hasPrimaryInstitutionType
Indicates that an entity’s main or principal institutional classification or category is of a specified type.
-
D.
supportsInstitutionType
Indicates that one entity provides backing, resources, or endorsement specifically for a particular type or category of institution.
-
E.
hasInstitutions
Indicates that one entity possesses, contains, or is associated with one or more institutions.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: April 28, 2026, 1:15 a.m.