Triple
T29895401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JD Gyms |
E759263
|
entity |
| Predicate | competitiveSegment |
P98858
|
FINISHED |
| Object | low-cost 24/7 gyms |
—
|
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: low-cost 24/7 gyms | Statement: [JD Gyms, competitiveSegment, low-cost 24/7 gyms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveSegment Context triple: [JD Gyms, competitiveSegment, low-cost 24/7 gyms]
-
A.
competitiveCategory
chosen
Indicates that two entities belong to the same market or activity segment in which they compete with one another.
-
B.
competitiveContext
Indicates a situation in which entities are engaged in or influenced by competition with one another.
-
C.
competitiveDifferentiator
Indicates that one entity possesses a distinguishing feature or advantage that sets it apart from comparable entities in a competitive context.
-
D.
competitiveImportance
Indicates the degree to which something holds strategic or competitive significance relative to alternatives or rivals.
-
E.
competitiveEffect
Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 6:04 p.m.