Triple
T5130550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Perfectos |
E115685
|
entity |
| Predicate | activeStatus |
P23338
|
FINISHED |
| Object | defunct |
—
|
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: defunct | Statement: [St. Louis Perfectos, activeStatus, defunct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeStatus Context triple: [St. Louis Perfectos, activeStatus, defunct]
-
A.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
B.
agencyStatus
chosen
Indicates the current operational or legal condition under which an agency or agent is functioning (e.g., active, inactive, suspended, or terminated).
-
C.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
D.
availabilityStatus
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
E.
activeAround
Indicates that an entity is performing actions or exhibiting activity in the vicinity of another entity or location.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.