Triple
T5392308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis City SC |
E120359
|
entity |
| Predicate | MLSStatus |
P62975
|
FINISHED |
| Object | expansion club |
—
|
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: expansion club | Statement: [St. Louis City SC, MLSStatus, expansion club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MLSStatus Context triple: [St. Louis City SC, MLSStatus, expansion club]
-
A.
propertyStatus
Indicates the current condition, state, or classification assigned to a property within a given context (e.g., availability, legal standing, or operational state).
-
B.
roofStatus
Indicates the current condition or state of a roof, such as whether it is intact, damaged, under repair, or replaced.
-
C.
soldProperty
Indicates that one entity transferred ownership of a property to another entity in exchange for payment.
-
D.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
E.
houseInvolved
Indicates that a house plays a significant role or is directly implicated in the specified event, situation, or relationship.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:04 p.m.