Triple
T13532306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa Tarpons |
E323162
|
entity |
| Predicate | adoptedNameIn |
P24880
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Tampa Tarpons, adoptedNameIn, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedNameIn Context triple: [Tampa Tarpons, adoptedNameIn, 2018]
-
A.
currentNameAdoptedBy
chosen
Indicates that an entity has adopted or started using a particular current name.
-
B.
adoptedFamilyName
Indicates that an entity has taken or been given a family name different from their original one, typically through adoption, marriage, or personal choice.
-
C.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
D.
adoptiveNomen
Indicates a naming relationship where one entity has taken on or been given the name of another in an adoptive or non-biological sense.
-
E.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbb34548190a6b44faa48125cd4 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.