Triple
T22944719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos García |
E569832
|
entity |
| Predicate | isUsedByProfessionGroup |
P53533
|
FINISHED |
| Object | athletes |
—
|
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: athletes | Statement: [Carlos García, isUsedByProfessionGroup, athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedByProfessionGroup Context triple: [Carlos García, isUsedByProfessionGroup, athletes]
-
A.
hasProfessionalGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular professional group or category.
-
B.
isAssociatedWithProfessionOfBearer
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
-
C.
usedByGroup
chosen
Indicates that something is utilized or employed by a particular group or collective entity.
-
D.
hasTypeOfWorkingGroup
Indicates that an entity is associated with or classified under a specific type or category of working group.
-
E.
isCommonInProfession
Indicates that something frequently occurs, appears, or is typical within a given profession or occupational field.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819c696c8190977bd2bca01509bc |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.