Triple
T2587538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte FC |
E58038
|
entity |
| Predicate | expansionStatus |
P40548
|
FINISHED |
| Object | MLS expansion team |
—
|
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: MLS expansion team | Statement: [Charlotte FC, expansionStatus, MLS expansion team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionStatus Context triple: [Charlotte FC, expansionStatus, MLS expansion team]
-
A.
explorationStatus
Indicates the current state or phase of an exploration process or activity between entities.
-
B.
acquisitionStatus
Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
-
C.
implementationStatus
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
-
D.
loreStatus
Indicates the canonical or contextual standing of something within a fictional or narrative universe (such as whether it is official, speculative, or non-canonical lore).
-
E.
distributionStatus
Indicates the current state or phase of how something is being distributed, such as whether distribution is planned, in progress, completed, or halted.
- F. None of above. chosen
Provenance (4 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3f8a3888190889c537e6df07305 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd37ef248819090ab6b86b67e355f |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.