Triple
T6515444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Atlantic League |
E148244
|
entity |
| Predicate | resumedNameUsage |
P59337
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [South Atlantic League, resumedNameUsage, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumedNameUsage Context triple: [South Atlantic League, resumedNameUsage, 1980]
-
A.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
B.
usesNameSince
chosen
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
C.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
D.
reserveName
Indicates that an entity secures or sets aside a specific name so that it cannot be used by others.
-
E.
nomenclaturalStatus
Indicates the formal taxonomic or naming status assigned to a scientific name (e.g., valid, invalid, synonym, provisional) within a nomenclatural system.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0d395081908fe6b1f9a912f095 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.